From jacoby.david at gmail.com Tue Aug 13 08:15:18 2013 From: jacoby.david at gmail.com (Dave Jacoby) Date: Tue, 13 Aug 2013 11:15:18 -0400 Subject: [Purdue-pm] Meeting In One Week Message-ID: Our next scheduled meeting is next Tuesday, in the newly refitted WSLR 116. Now begins our weekly "Does anyone have anything to talk about?" I have scraped the Purdue CS Colloquium Calendar web page and transferred it to vCal ( http://pm.purdue.org/~jacoby/cs_colloquia.ics ) and talk some on the confusion of the vCal standard, the need for the Semantic Web and the joy of Template Toolkit. I have also started using the feature 'state' and did some benchmarking. It's a lightning talk at best, but it's something. Anyone else doing something new with Perl? Any other dynamic language? There is also some interest in establishing this as a Google Hangout sort of thing. None of my cameras are good enough to really do that. Any interest in working out that tech? -- David Jacoby jacoby.david at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From westerman at purdue.edu Tue Aug 13 08:23:05 2013 From: westerman at purdue.edu (Rick Westerman) Date: Tue, 13 Aug 2013 11:23:05 -0400 (EDT) Subject: [Purdue-pm] Meeting In One Week In-Reply-To: Message-ID: <131236342.5771.1376407385083.JavaMail.root@mailhub016.itcs.purdue.edu> > Anyone else doing something new with Perl? I've been playing around with IO::All. It is an interesting module by IngyDotNet -- Rick Westerman westerman at purdue.edu Bioinformatics specialist at the Genomics Facility. Phone: (765) 494-0505 FAX: (765) 496-7255 Department of Horticulture and Landscape Architecture 625 Agriculture Mall Drive West Lafayette, IN 47907-2010 Physically located in room S049, WSLR building From gizmo at purdue.edu Wed Aug 21 12:14:08 2013 From: gizmo at purdue.edu (Joe Kline) Date: Wed, 21 Aug 2013 15:14:08 -0400 Subject: [Purdue-pm] When storing a past event... Message-ID: <52151180.50104@purdue.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 "When storing a past event, always convert it into UTC and store it that way (I knew that). But when storing a future event (esp. if it's more than a year in the future), store it in the local timezone and only convert to UTC on the given day. This way you can properly handle the changes to time zones and/or daylight savings that might happen in the meantime" - From domm's notes on YAPC::EU that happened like last week in Kiev. http://domm.plix.at/perl/2013_08_things_i_learned_at_yapc_europe_2013.html Lots of good stuff in his summary, but not all talk slides are online. joe -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlIVEYAACgkQb0mzA2gRTplT3wCdEbND4kEOfAuUaH/yK+KYvG5Z eNUAnAhCZN6xSy3c5F3D2PlteEKCudCf =ohyj -----END PGP SIGNATURE----- From jacoby at purdue.edu Thu Aug 29 13:04:03 2013 From: jacoby at purdue.edu (Dave Jacoby) Date: Thu, 29 Aug 2013 16:04:03 -0400 Subject: [Purdue-pm] Libraries have me befuddled Message-ID: <521FA933.8000108@purdue.edu> I've hit some weirdness in a software migration. So, I've set it up so I'm adding my libs to the PERL5LIB environment variable instead of 'use lib "foo"', so I can move 'em into production without changing a 'use lib' line in more than a dozen modules. When I'm using libraries directly, this is turning out fine. But, part of what I'm doing is putting commonly used functions in one module and using them in another. So, I have SecGenTools::Run. It has six other SecGenTools modules. use SecGenTools::CV ; use SecGenTools::Misc ; use SecGenTools::Operator ; use SecGenTools::Recipe ; use SecGenTools::Accession ; use SecGenTools::Request ; In general, my modules start with: use Exporter qw(import) ; our @EXPORT ; our %EXPORT_TAGS ; our @EXPORT_OK ; BEGIN { @EXPORT = qw{ subroutine_1 subroutine_2 subroutine_3 } ; %EXPORT_TAGS = ( 'all' => [ @EXPORT ] ) ; @EXPORT_OK = ( @{ $EXPORT_TAGS{ 'all' } } ) ; } The point being, there is code written against the libs that existed before I understood more than I do now. Used to be that you'd do this: use SecGenTools::CV ':all' ; or, more rarely: use SecGenTools::CV 'make_analysis_types' ; but I want to move to this most of the time. use SecGenTools::CV ; I'm trying to test Run.pm, and I'm finding that this works: use SecGenTools::CV ':all' ; and that this works: use lib '/home/djacoby/dev/Tools/lib' ; use SecGenTools::CV ; but this does not: use SecGenTools::CV ; Undefined subroutine &SecGenTools::Run::get_accession_data called at /home/djacoby/dev/Tools/lib/SecGenTools/Run.pm line 510. I'm trying to pull this into repeatable chunks, so I can begin to dig in and find the solution, but as is, I'm befuddled. -- Dave Jacoby Code Maker, Purdue Genomics Core Lab http://web.ics.purdue.edu/~djacoby 221 days until the end of XP support http://www.accidentalcreative.com/creating/boycott-unnecessary-complexity