Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Ovid (2709)

  (email not shown publicly)
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Tuesday May 21, 2002
03:32 PM


[ #5123 ]

Woo hoo! Just submitted my first patch to p5p. It appears that was untainting data from STDIN. Whoops! I also discovered the same problem in Text::ParseWords and tried to email a patch to the author, only to find out that his email is inactive. Humph!

Update: I also submitted a patch for Text::ParseWords and am pleased to announce that both patches will be in 5.8.0 :)

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • My first patch [] was a doc patch. In fact almost all of my patches have been doc patches, or adding a $VERSION to a core module. I do have one script [] in /Porting that checks to make sure core modules have a $VERSION.

    Nothing too major, but still fun! Be sure to keep looking for other places to contribute also!
  • My first patch (and my only one so far) was the patch that makes sure you can type perl5.6.1 Makefile.PL and it will definitely pick up /path/to/perl5.6.1 instead of /different/path/to/earlier/perl. Believe it or not, with 5.6.0 and earlier, you could do perl5.6.0 Makefile.PL but when you went on to do make && make install you would pick up whatever perl was first in (your PATH + some other dirs), regardless of version or even name. The only way to guarantee the module built with the Perl you want

    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers