"I estimate that it would take approximately 2000 CPU years to smoke all of CPAN on a reasonable set of platforms." -- Adam Kennedy, 2000 light years from home.
[summariser's note: the week was too busy for me to spend the required time to bring the summary to a close, so here's the best I could do. Regretfully, I am unable to summarise Nicholas Clark's excellent follow-ups to the Perl 5 advocacy thread that was kicked off the week before. Interested readers are invited to dive back into the thread to chase them down.]
Once upon a time http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-06/msg00477.html
This was in some ways fall-out from the advocacy thread last week. By bringing this module into core, it would ease installing CPAN modules on the new non-ActiveState Windows-based Perl distributions that are coming to light (that is, distributions that don't use ActiveState's
ppm installer but instead use source tarballs directly from CPAN).
Dave Mitchell reported that he reworked the
TRIE regop to work with the new state stack mechanism, thereby removing more recursion from the regular expression engine. Yves Orton was impressed that Dave taken Yves's code in his stride, and announced that he was planning to introduce another regop in the future for other kinds of tries.
Going cursive http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-06/msg00903.html
Yves Orton followed up on a question Tels asked last week, about benchmarking regular expression performance
A fair fight http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-06/msg00664.html
It used to be that if a thread was still running at
exit time, a warning was generated. So a patch was written to suppress it. Jerry D. Hedden questioned the rationale, pointing out that someone, somewhere, might find this useful sometime.
He thought that a nicer way of dealing with this would be via
no warnings 'threads', except that it doesn't work. Rafael Garcia-Suarez explained what hoops one would have to jump through in the C source to do so. Jerry noted that the different functions Rafael cite are not documented, and wanted to know what the differences were between them. Rafael explained the differences, and suggested looking through the source for a sample of uses.
A fair warning http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-06/msg00658.html
In other threads news, Jerry also discovered how a small thread that does nothing but
exit will not call the
PL_threadhook handler and wondered what to do about it. Jan Dubois thought that the best thing to do would be to put the thread running code in a
Tom Horsley kicked off a thread about testing CPAN.
First steps in implementing the zip64 algorithm in Perl. As there is no real reference implementation, and the specs are vague in places, Paul Marquess kicked this out the door to see whether it flies or smokes.
The 64 bit question http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-06/msg00714.html
Andy Lester pulled some variables down into tighter scopes in regexec.c, in an attempt to make it easier to read and follow.
Bedtime reading http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-06/msg00631.html
A sensible improvement to perlhack.pod from Dr. Ruud.
A couple of smokes drew some comments.
Dominic Dunlop followed up on this April bug with some cogent analysis that pinned the blame on calling
die() within a signal handler, but lacked the time to dig more deeply into the problem.
Rafael applied bcarter's patch to fix this problem, and added a regression test to make sure it never comes back.
Dominic and Yves went the extra mile to help solve this problem, even though it had nothing to do with p5p's charter.
Chris at financial was having a problem (like a segfault) with the
CentOS packages of
perl and asked for help. Nicholas regretted to announce that he didn't have the faintest idea what was happening, and suggested either trying to reproduce the problem using only core modules, or asking
CentOS for support.
Sadahiro Tomoyuki and Dominic Dunlop raced each other to see who could develop the best patch for this bug in the shortest possible time (some issue with formatting v-strings). In the process, it appears that Ravi S. Kadali from IBM is able to run smoke tests against
blead on the z/OS platform. This will do wonders for smoking out EBCDIC oddities.
Keith Doyle found that multiple threads that backtick or popen kids will hang at random, which is admittedly less than ideal. Unfortunately he received no feedback on the issue.
Jie Gao discovered a problem with op/getppid.t on
maint. Dominic thought that the test from
blead, which has been rewritten, would possibly do the tricked and asked Jie Gao to take it for a spin, to see if it resolved the failure.
Alex Keim had a problem on the Win32 platform with environments approaching or exceeding 32K in size. Steve Hay was able to reproduce the problem and found that it only manifested itself in threaded builds. Jan Dubois and Dr. Ruud suggested some other workarounds (basically, use a file, memory-mapped or otherwise, rather than the environment to pass large slabs of data to kids).
Alex still found that an environment that gave
cmd (the Win32 shell) no trouble caused Perl grief, pointing to a problem with perl's environment handling.
A "cannot happen" bug in
Text::Wrap surfaced with this bug report. Dominic chose to punt the issue for a while, to see what the current maintainer of the module had to say.
Laurent had a strange problem with a tarball for perl 5.8.8 that seemed to be lacking a couple of example files, according to the manifest. Dominic offered what advice he could.
Erik R. Ogan discovered that 5.8.8 would fail to match a string that ought to have 32767 characters matched by
Funny about that http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-06/msg00871.html
Ravi kumar Ravi had some problems with protocol name resolution causing a handful of tests to failed. No followups.
Jerry D. Hedden's latest patch to the threads library makes use of a few functions (
JMPENV_POP) that are not available when compiling ActiveState Perl from source.
+ 5 - 2 = 1493 http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-06/msg00642.html The List http://rt.perl.org/rt3/NoAuth/perl5/Overview.html
Sys-Syslogversion 0.16 uploaded by Sébastien Aperghis-Tramoni, and Rafael updated
bleadwith this version.
This in turn allowed Sébastien to close a couple of old bugs:
#20557 http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-06/msg00773.html #35406 http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-06/msg00771.html
CPANPLUSversion 0.072 was uploaded to CPAN by Jos Boumans. No, it's not core, but may be one day. The fact that overall RAM usage has declined in this release (as per the release notes) is certainly a welcome step in this direction.
- A sleeker
Devel::PPPortversion 3.08_06 was integrated into
bleadby Marcus Holland-Moritz. He shrunk the size of the tarball significantly, by generating PPPort.pm and PPPort.xs on the fly during the build. On the other hand, this cause
Configureto come to grief, since as it didn't see a PPPort.xs at the beginning, it went ahead and built the non-XS version.
Philippe M. Chiasson tracked down and reinstated the missing files from the APC archive.
Full recovery http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-06/msg00670.html
Nicholas Clark thought of a way of sidestepping the bogosity introduced by the Intel
icc compiler pretending to be
Almost but not quite more than we deserve http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-06/msg00936.html
Tom Christiansen wrote about the legibility myth and it sparked off an interesting discussion about typography and the written word.
Tom also continued with a discussion of parenthetical perils.
Dr Ruud cooked up a tiny patch for toke.c to fix
isALNUM(*s) && *s != '_'.
Paul Marquess solved a problem in
make test with multiple Makefile.PLs.
Need to know http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-06/msg00792.html
Paul also wondered why
-w don't work as expected when applied to
\*STDOUT on Win32.
David Landgren ran a smoke at one point last week and reported a few failures in the maint snapshot. Hmm, maybe after I get the summary out the door I'll go and see what's happening with it now.
John E. Malmberg wanted to know if the rsync server was stuck at
Feel free to follow the links if the subject grabs your attention.
This summary was written by David Landgren. The paragraph reformatter
fmt(1) that comes with my OS is not 8-bit clean, and it ate the "é" in Sébastien Aperghis-Tramoni name in the previous summary. My apologies to Sébastien. I hear there's a text processing language that is good at doing this sort of stuff...
If you want a bookmarklet approach to viewing bugs and change reports, there are a couple of bookmarklets that you might find useful on my page of Perl stuff:
Weekly summaries are published on http://use.perl.org/ and posted on a mailing list, (subscription: email@example.com). The archive is at http://dev.perl.org/perl5/list-summaries/. Corrections and comments are welcome.
If you found this summary useful, please consider contributing to the Perl Foundation to help support the development of Perl.