|laziness, impatience, and hubris|
What? I patched Perl?by japhy (Canon)
|on Jul 12, 2001 at 08:05 UTC||Need Help??|
sierrathedog04 was baffled recently about me saying I was going to patch Perl. Allow me to shed some light on the subject.
To patch Perl, you don't need to know very much C -- rather, you need to know a lot of perl. No, not Perl, but perl. The code for perl is written in C, and there are more macros in the code than you can imagine. I've never done any really involving work with the perl source code, but I plan to in the future.
The problem I worked on most recently was putting a warning around the use of the /o modifier with a qr// object. There were several places that needed patching:
As for submitting the patch, P5P (the Perl5-Porters) prefer patches in "universal diff" format (diff -u OLD NEW). After submitting my patch to firstname.lastname@example.org, feedback comes in about something that I may not have handled correctly, or suggesting a different course of action. Finally, after things work and people are happy, Jarkko, the Perl Patch Pumpking, lets me know that my patch has been "applied, thanks."
What Perl did I patch? The most recent "snapshot" of version 5.7.1, also known as "bleadperl". This is the development branch of Perl 5.6.1, indicated by the odd number. (When Perl 5.8 comes out, development will occur in 5.9.)
For more information, read the perlhack.pod documentation, found in the Perl 5.6 docs.
japhy -- Perl and Regex Hacker