From gizmo at purdue.edu Tue Apr 13 14:13:30 2010 From: gizmo at purdue.edu (Joe Kline) Date: Tue, 13 Apr 2010 17:13:30 -0400 Subject: [Purdue-pm] 5.12.0 out Message-ID: <4BC4DE7A.1000102@purdue.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In case you missed it 5.12 is out. http://search.cpan.org/~jesse/perl-5.12.0/ Some rather interesting changes: http://search.cpan.org/~jesse/perl-5.12.0/pod/perl5120delta.pod Some of the most interesting: The yada yada operator implicit strictures Unicode improvements Y2038 compliance Pluggable keywords (this looks really scary powerful...for those that understand it) smart match changes compress::raw::bzip2 now a core module new documentation on performance techniques http://search.cpan.org/~jesse/perl-5.12.0/pod/perlperf.pod Like most releases I might wait for 5.12.1 to come out but I think they learned from the pain of 5.10.0 so it is probably rather usable...we'll see. joe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org iD8DBQFLxN56b0mzA2gRTpkRAnR3AJ0UfdO4bP+Bn1gnjAkOeWwgj8nUzQCfZgRz 78+z81vCR4VFeixJmxPNu8Q= =j3Zw -----END PGP SIGNATURE----- From mdw at purdue.edu Tue Apr 13 14:18:25 2010 From: mdw at purdue.edu (Mark Daniel Ward) Date: Tue, 13 Apr 2010 17:18:25 -0400 Subject: [Purdue-pm] 5.12.0 out In-Reply-To: <4BC4DE7A.1000102@purdue.edu> References: <4BC4DE7A.1000102@purdue.edu> Message-ID: <4BC4DFA1.4000902@purdue.edu> Dear Joe, Thank you for letting us know! Mark On 4/13/10 5:13 PM, Joe Kline wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > In case you missed it 5.12 is out. > > http://search.cpan.org/~jesse/perl-5.12.0/ > > Some rather interesting changes: > > http://search.cpan.org/~jesse/perl-5.12.0/pod/perl5120delta.pod > > Some of the most interesting: > > The yada yada operator > > implicit strictures > > Unicode improvements > > Y2038 compliance > > Pluggable keywords (this looks really scary powerful...for those that > understand it) > > smart match changes > > compress::raw::bzip2 now a core module > > new documentation on performance techniques > http://search.cpan.org/~jesse/perl-5.12.0/pod/perlperf.pod > > Like most releases I might wait for 5.12.1 to come out but I think they > learned from the pain of 5.10.0 so it is probably rather usable...we'll see. > > joe > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (GNU/Linux) > Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org > > iD8DBQFLxN56b0mzA2gRTpkRAnR3AJ0UfdO4bP+Bn1gnjAkOeWwgj8nUzQCfZgRz > 78+z81vCR4VFeixJmxPNu8Q= > =j3Zw > -----END PGP SIGNATURE----- > _______________________________________________ > Purdue-pm mailing list > Purdue-pm at pm.org > http://mail.pm.org/mailman/listinfo/purdue-pm > > From mark at purdue.edu Mon Apr 19 06:12:21 2010 From: mark at purdue.edu (Mark Senn) Date: Mon, 19 Apr 2010 09:12:21 -0400 Subject: [Purdue-pm] a one question survey Message-ID: <20373.1271682741@pier.ecn.purdue.edu> Gabor Szabo (http://szabgab.com/) wrote Please forward this request to your pm group if you feel it appropriate. Please take the 5 sec to answer this question on the new poll I setup: http://perlide.org/poll201004/ and send this request to the other people using Perl in your company. Mark Senn From mdw at purdue.edu Mon Apr 19 07:44:57 2010 From: mdw at purdue.edu (Mark Daniel Ward) Date: Mon, 19 Apr 2010 10:44:57 -0400 Subject: [Purdue-pm] a one question survey In-Reply-To: <20373.1271682741@pier.ecn.purdue.edu> References: <20373.1271682741@pier.ecn.purdue.edu> Message-ID: <4BCC6C69.1090001@purdue.edu> Dear Purdue PM friends, Did anyone install Perl 5.12 on their Mac last week? I've installed Perl by hand on my Mac in the past (for instance, when Perl 5.10 was released), but I wanted to check and see if anybody had tried it yet. I'm always cautious about such things, because I don't want to break the Apple pre-installed Perl, which is 5.10.0 in Mac OS X 10.6.3. Any suggestions/advice or lessons learned? Tips? Mark On 4/19/10 9:12 AM, Mark Senn wrote: > Gabor Szabo (http://szabgab.com/) wrote > > Please forward this request to your pm group if you feel it appropriate. > > Please take the 5 sec to answer this question on the new poll I setup: > > http://perlide.org/poll201004/ > > and send this request to the other people using Perl in your company. > > Mark Senn > _______________________________________________ > Purdue-pm mailing list > Purdue-pm at pm.org > http://mail.pm.org/mailman/listinfo/purdue-pm > > From mdw at purdue.edu Mon Apr 19 07:45:02 2010 From: mdw at purdue.edu (Mark Daniel Ward) Date: Mon, 19 Apr 2010 10:45:02 -0400 Subject: [Purdue-pm] a one question survey In-Reply-To: <20373.1271682741@pier.ecn.purdue.edu> References: <20373.1271682741@pier.ecn.purdue.edu> Message-ID: <4BCC6C6E.2080408@purdue.edu> Dear Purdue PM friends, Did anyone install Perl 5.12 on their Mac last week? I've installed Perl by hand on my Mac in the past (for instance, when Perl 5.10 was released), but I wanted to check and see if anybody had tried it yet. I'm always cautious about such things, because I don't want to break the Apple pre-installed Perl, which is 5.10.0 in Mac OS X 10.6.3. Any suggestions/advice or lessons learned? Tips? Mark On 4/19/10 9:12 AM, Mark Senn wrote: > Gabor Szabo (http://szabgab.com/) wrote > > Please forward this request to your pm group if you feel it appropriate. > > Please take the 5 sec to answer this question on the new poll I setup: > > http://perlide.org/poll201004/ > > and send this request to the other people using Perl in your company. > > Mark Senn > _______________________________________________ > Purdue-pm mailing list > Purdue-pm at pm.org > http://mail.pm.org/mailman/listinfo/purdue-pm > > From westerman at purdue.edu Mon Apr 19 07:52:40 2010 From: westerman at purdue.edu (Rick Westerman) Date: Mon, 19 Apr 2010 10:52:40 -0400 (EDT) Subject: [Purdue-pm] Meeting tomorrow, Tues Apr 20th In-Reply-To: <26673095.1612.1271688661702.JavaMail.root@mailhub011.itcs.purdue.edu> Message-ID: <5181663.1614.1271688760135.JavaMail.root@mailhub011.itcs.purdue.edu> Our normal monthly meeting is tomorrow, Tuesday Apr. 20th in WSLR 116. 11:30 lunch, noon start of talks. We do not have anything scheduled but rumor is that Mike will may give a talk on C vs. Perl. Other comments (especially for the new release) would be appreciated. -- 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 Mon Apr 19 08:51:45 2010 From: gizmo at purdue.edu (Joe Kline) Date: Mon, 19 Apr 2010 11:51:45 -0400 Subject: [Purdue-pm] a one question survey In-Reply-To: <4BCC6C6E.2080408@purdue.edu> References: <20373.1271682741@pier.ecn.purdue.edu> <4BCC6C6E.2080408@purdue.edu> Message-ID: <4BCC7C11.2090106@purdue.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark Daniel Ward wrote: > Dear Purdue PM friends, > Did anyone install Perl 5.12 on their Mac last week? I've installed > Perl by hand on my Mac in the past (for instance, when Perl 5.10 was > released), but I wanted to check and see if anybody had tried it yet. > I'm always cautious about such things, because I don't want to break > the Apple pre-installed Perl, which is 5.10.0 in Mac OS X 10.6.3. > Any suggestions/advice or lessons learned? Tips? Mark, here are a couple of posts from brian d foy and a book excerpt that look to be useful for non-os Perl installs: - From the upcoming Effective Perl Programming 2nd Edition ==================================================================== (the formatting sucks a bit because it's from a pdf brian gave us a Frozen Perl). Item 110. Compile and install your own perls. Sometimes Perl suffers from its own success. It comes with just about every version of operating systems with Unix or Linux heritages, including Mac OS X. Many of these systems use Perl as part of their normal operation or provide perl as packages. Even then, you can find pre-compiled perls for most platforms. Perl on Windows commonly uses precompiled binaries from ActiveState (http://www.activestate.com), cygwin, or Strawberry Perl (http://www.strawberryperl.com). People don?t have to compile their own perl anymore. There are many advantages to compiling and using your own perl, though. Since many operating systems rely on perl for normal maintenance tasks, you want to avoid anything that will break that perl. If you upgrade a core module, for instance, an important part of the system may stop working. You probably want to pretend that the system perl is not even there. Also, as a Perl developer, you should install several versions of perl so you can test against each of them. It?s easy to install and maintain distinct versions. This Item covers the basics, but your system may have additional requirements. The perl distribution has several README files that give instructions for particular operating systems. Compiling your perl To compile perl, you?ll need a C compiler and the build tools that typically come with it. You?ll also need make or one of its variants. You don?t need any special privileges, and you can install perl in your own user directory. This Item assumes you have all of that already worked out. To start, download the version of perl that you want to test. You can find all of the perl releases on CPAN (http://www.cpan.org/src/README.html). Once you unpack your distribution, change into its directory. It?s time to choose an installation location. For this example, you?ll put all of your perls under /usr/local/perls, and each new installation will get its own subdirectory under that. The Configure script examines your system and prepares the perl sources for compilation. The -des switches accept all of the default answers and gives you terse output. The -D switch overrides one of the answers, in this case for prefix which sets the installation location. % ./Configure -des -Dprefix=/usr/local/perls/perl-5.10.1 In this case, you?ve configured the build to install everything under /usr/local/perls/perl-5.10.1. By accepting the defaults, you won?t move the perl into /usr/bin, so don?t be afraid of messing up anything. You should probably do this from an unprivileged account anyway, so your system will stop you from doing anything too bad. If you want to see everything that you can configure, don?t accept any of the defaults and go through the entire process yourself (try it once in life): % ./Configure After you run the Configure, no matter which options you used, you?re ready to build the source. Depending on your system, you?ll need a make variant: % make all When the build completes, you can test it, which might take a while: % make test And finally, you install it. You should see it copy files into the directory you specified in prefix: % make install After you finish installing that perl, try installing another one. You can enable different features, such as threads. You can change the prefix to note the interesting feature of this perl: % ./Configure -des -Dusethreads \ - -Dprefix=/usr/local/perls/perl-5.10.1-threaded Using your perl Once you install perl there?s nothing left for you to configure to use it, although you have to use the path to the perl you want to use. You can see the default module search path, for instance: % /usr/local/perls/perl-5.10.1/bin/perl -V All of the tools, extra programs, and modules for your new perl show up under your prefix directory. If you want cpan to install modules for this perl, you call the cpan for that perl. It?s in the bin directory under your prefix: % /usr/local/perls/perl-5.10.1/bin/cpan LWP::Simple Any modules that you install in this fashion go into the library directories just for that perl and do not disturb any other installation. Indeed, that?s the point. Remember that when you switch to using another perl: you might have to reinstall the modules for that perl too. If you want to read the documentation, you use the right path to perldoc so it searches the correct module path: % /usr/local/perls/perl-5.10.1/bin/perldoc? LWP::Simple If you want to use this perl and its tools as your main perl, you can add its path to your PATH environment variable. That leaves the system perl in place, too. If you want to switch your default perl, you just update your path so the shell finds the new default first. Everything else, including the module paths, take care of themselves. You might have some trouble with CPAN.pm or CPANPLUS, since they store their configuration in your home directory (Item 65). Their configurations are per-user instead of per-perl. Ensure that you update their configuration for the perl that you want to use. Things to remember ? Install your own perl so you don?t disturb the system perl. ? You can install multiple perls with different configurations. ? Add your preferred Perl?s location to your PATH to make it the default. ==================================================================== Manager Perl modules with git http://www.effectiveperlprogramming.com/blog/60 Links for per-version tools http://www.effectiveperlprogramming.com/blog/92 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org iD8DBQFLzHwQb0mzA2gRTpkRAhgRAJ4lZiF4+KtEt5r5xJHHWmNiZUPIJQCfZtKb enAGsZiK1VOJWJ9ZVEVALGs= =UqVC -----END PGP SIGNATURE----- From gizmo at purdue.edu Mon Apr 19 08:53:05 2010 From: gizmo at purdue.edu (Joe Kline) Date: Mon, 19 Apr 2010 11:53:05 -0400 Subject: [Purdue-pm] Meeting tomorrow, Tues Apr 20th In-Reply-To: <5181663.1614.1271688760135.JavaMail.root@mailhub011.itcs.purdue.edu> References: <5181663.1614.1271688760135.JavaMail.root@mailhub011.itcs.purdue.edu> Message-ID: <4BCC7C61.3030001@purdue.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rick, I might have my "pre-release" review of Effective Perl Programming ready (or I might just do an overview of "This month in Perl blogs which might cover 5.12, but probably not since I haven't had a chance to play with it). joe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org iD8DBQFLzHxgb0mzA2gRTpkRAm/mAJ9n+TgH64O7cEe+y8WRIoXDpC/UPQCfWL2Q cTwqNenXS9OxyhxxEGdJq5E= =Y9Q2 -----END PGP SIGNATURE----- From mdw at purdue.edu Mon Apr 19 08:57:52 2010 From: mdw at purdue.edu (Mark Daniel Ward) Date: Mon, 19 Apr 2010 11:57:52 -0400 Subject: [Purdue-pm] a one question survey In-Reply-To: <4BCC7C11.2090106@purdue.edu> References: <20373.1271682741@pier.ecn.purdue.edu> <4BCC6C6E.2080408@purdue.edu> <4BCC7C11.2090106@purdue.edu> Message-ID: <4BCC7D80.5090906@purdue.edu> Dear Joe, That is very helpful. Thank you so much! Mark On 4/19/10 11:51 AM, Joe Kline wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Mark Daniel Ward wrote: > >> Dear Purdue PM friends, >> Did anyone install Perl 5.12 on their Mac last week? I've installed >> Perl by hand on my Mac in the past (for instance, when Perl 5.10 was >> released), but I wanted to check and see if anybody had tried it yet. >> I'm always cautious about such things, because I don't want to break >> the Apple pre-installed Perl, which is 5.10.0 in Mac OS X 10.6.3. >> Any suggestions/advice or lessons learned? Tips? >> > > Mark, > > here are a couple of posts from brian d foy and a book excerpt that look > to be useful for non-os Perl installs: > > > - From the upcoming Effective Perl Programming 2nd Edition > ==================================================================== > (the formatting sucks a bit because it's from a pdf brian gave us a > Frozen Perl). > > Item 110. Compile and install your own perls. > > Sometimes Perl suffers from its own success. It comes with just about > every version of operating systems with Unix or Linux heritages, > including Mac OS X. Many of these systems use Perl as part of their > normal operation or provide perl as packages. Even then, you can find > pre-compiled perls for most platforms. > > Perl on Windows commonly uses precompiled binaries from ActiveState > (http://www.activestate.com), cygwin, or Strawberry Perl > (http://www.strawberryperl.com). People don?t have to compile their own > perl anymore. > > There are many advantages to compiling and using your own perl, though. > Since many operating systems rely on perl for normal maintenance tasks, > you want to avoid anything that will break that perl. If you upgrade a > core module, for instance, an important part of the system may stop > working. You probably want to pretend that the system perl is not even > there. > > Also, as a Perl developer, you should install several versions of perl > so you can test against each of them. It?s easy to install and maintain > distinct versions. This Item covers the basics, but your system may have > additional requirements. The perl distribution has several README files > that give instructions for particular operating systems. > > Compiling your perl > > To compile perl, you?ll need a C compiler and the build tools that > typically come with it. You?ll also need make or one of its variants. > You don?t need any special privileges, and you can install > perl in your own user directory. This Item assumes you have all of that > already worked out. > > To start, download the version of perl that you want to test. You can > find all of the perl releases on CPAN (http://www.cpan.org/src/README.html). > > Once you unpack your distribution, change into its directory. It?s time > to choose an installation location. For this example, you?ll put all of > your perls under /usr/local/perls, and each new installation will get > its own subdirectory under that. > > The Configure script examines your system and prepares the perl sources > for compilation. The -des switches accept all of the default answers and > gives you terse output. The -D switch > overrides one of the answers, in this case for prefix which sets the > installation location. > > % ./Configure -des -Dprefix=/usr/local/perls/perl-5.10.1 > > In this case, you?ve configured the build to install everything under > /usr/local/perls/perl-5.10.1. By accepting the defaults, you won?t move > the perl into /usr/bin, so don?t be afraid of messing up anything. You > should probably do this from an unprivileged account anyway, so your > system will stop you from doing anything too bad. > > If you want to see everything that you can configure, don?t accept any > of the defaults and go through the entire process yourself (try it once > in life): > > % ./Configure > > After you run the Configure, no matter which options you used, you?re > ready to build the source. Depending on your system, you?ll need a make > variant: > > % make all > > When the build completes, you can test it, which might take a while: > > % make test > > And finally, you install it. You should see it copy files into the > directory you specified in prefix: > > % make install > > After you finish installing that perl, try installing another one. You > can enable different features, such as threads. You can change the > prefix to note the interesting feature of this perl: > > % ./Configure -des -Dusethreads \ > - -Dprefix=/usr/local/perls/perl-5.10.1-threaded > > Using your perl > > Once you install perl there?s nothing left for you to configure to use > it, although you have to use the path to the perl you want to use. You > can see the default module search path, for instance: > > % /usr/local/perls/perl-5.10.1/bin/perl -V > > All of the tools, extra programs, and modules for your new perl show up > under your prefix directory. If you want cpan to install modules for > this perl, you call the cpan for that perl. It?s in the bin directory > under your prefix: > > % /usr/local/perls/perl-5.10.1/bin/cpan LWP::Simple > > Any modules that you install in this fashion go into the library > directories just for that perl and do not disturb any other > installation. Indeed, that?s the point. Remember that when you switch to > using another perl: you might have to reinstall the modules for that > perl too. > > If you want to read the documentation, you use the right path to perldoc > so it searches the correct module path: > > % /usr/local/perls/perl-5.10.1/bin/perldoc? > LWP::Simple > > If you want to use this perl and its tools as your main perl, you can > add its path to your PATH environment variable. That leaves the system > perl in place, too. If you want to switch your default perl, you just > update your path so the shell finds the new default first. Everything > else, including the module paths, take care of themselves. > > You might have some trouble with CPAN.pm or CPANPLUS, since they store > their configuration in your home directory (Item 65). Their > configurations are per-user instead of per-perl. Ensure that you update > their configuration for the perl that you want to use. > > Things to remember > ? Install your own perl so you don?t disturb the system perl. > ? You can install multiple perls with different configurations. > ? Add your preferred Perl?s location to your PATH to make it the default. > ==================================================================== > > Manager Perl modules with git > http://www.effectiveperlprogramming.com/blog/60 > > Links for per-version tools > http://www.effectiveperlprogramming.com/blog/92 > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (GNU/Linux) > Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org > > iD8DBQFLzHwQb0mzA2gRTpkRAhgRAJ4lZiF4+KtEt5r5xJHHWmNiZUPIJQCfZtKb > enAGsZiK1VOJWJ9ZVEVALGs= > =UqVC > -----END PGP SIGNATURE----- > _______________________________________________ > Purdue-pm mailing list > Purdue-pm at pm.org > http://mail.pm.org/mailman/listinfo/purdue-pm From gizmo at purdue.edu Tue Apr 20 12:28:53 2010 From: gizmo at purdue.edu (Joe Kline) Date: Tue, 20 Apr 2010 15:28:53 -0400 Subject: [Purdue-pm] Top 100 competition Message-ID: <4BCE0075.30004@purdue.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Here are the links regarding the Mojo vs. Dancer Top 100 competition Week 1: rules and such http://use.perl.org/~Alias/journal/40292 Week 2 http://use.perl.org/~Alias/journal/40312 joe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org iD8DBQFLzgB1b0mzA2gRTpkRAuA3AJ0ekHfaCD810+zn5QLedI9j/+cdKgCfQNUf D2RhIaNveSzJs9cb6IwWkvs= =bcrW -----END PGP SIGNATURE-----