Let's change perl's internal hash function, shall we?
Vadim reminded the patch-meisters, (and clearly the man has been revising his classics) to apply the large Win32 patch that Yves Orton had posted, so that they could continue the process.
Smelly socks! http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00098.html
Which must have been applied, for a little while later Vadim posted further tweaks to the Wince side of things.
One less source file! http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00139.html
As well as some Makefile.ce goodness
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00170.html
state variables featured in bleadRafael Garcia-Suarez ironed out some of the bigger show-stoppers in his state variable work, and was thus able to commit the first draft to blead. Arrays and hashes aren't done yet, but as of now, we have an elegant solution to the perennial my $var if 0 problem.
Nicholas Clark was impressed, and tried out a snippet of code, that Rafael turned into a test for a brand new t/op/state.pl.
Coup d'état http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00149.html
socketpair available everywhere?Jan Dubois was looking at the section in perlport where it says that socketpair is not available on Win32 and a number of other platforms. He thought that it was currently emulated on all platforms that did not provide a native implementation. If so, it would mean that the section could be quietly dropped.
Alex Waugh mentioned that it's available natively on RISC OS, so if nothing else, that could be removed from the list.
Going native http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00155.html
Anno Siegel delivered a two part patch to improve the implementation of inside-out classes. Part one deals with perl itself, and the second part reaches out into the core library and expands Hash::Util. Anno also provided a demo to show how it worked.
Yves Orton was quite enthusiastic, Randy W. Sims, markedly less. David Golden had a close look at the patch and explained clearly what he thought was going on, and pointed out some issues where the implementation was a bit rough around the edges.
Yuval Kogman thought the patch was maybe not general enough, and suggested some avenues to explore, other than just Inside-Out objects. David Golden and Abigail discussed issues such as backwards compatibility at length.
Rafael announced that he was happy with the intent of the patch. Nicholas Clark caught an error that Anno set about correcting.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00148.html
Obligingly, Anno summarised where he was going from here with the patch. In the end he retired the patch and set about doing something better.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00272.html "U" magic in February http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-02/msg00246.html
Jarkko Hietaniemi was looking at hash functions, and stumbled across a page full of them. Perl uses the "One-at-a-Time" algorithm. Except that we don't, although the comments say we do. Except, if you have enough coffee and look again, we really do.
Yves Orton benchmarked a series of hashing algorithms to see what they did for perl. At a first glance, it looked like "One-at-a-Time" was rather slow, especially in comparison to another hashing function named (surprise!) SuperFastHash.
Much of the improvement is dependent on the length of the hash keys. Short keys show little difference, long keys can show spectacular improvements.
Michael Schroeder weighed in with Buzhash, which, at the expense of a table of 256 ints, boils down to a rotate and xor per character.
Total Hash Controversy http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00261.html
select((select(OUTPUT_HANDLE), $| = 1)[0])Abigail made an impassioned plea to keep this tricky construct in the documentation. The main point being that it would be of use to maintenance programmers, not necessarily for people starting out. A few people argued the issue back and forth, and Abigail maintained that a three line snippet would be preferable, since people could pick it apart and thus learn more easily about the particular parts they are unsure of.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00197.html
Jerry D. Hedden sent in a new version of a patch to threads, this time with much less drastic whitespace reformatting. This time around it was applied.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00146.html
... and another to add stack size support, which was the main reason why Jerry started to work on all of this in the first place. Applied as well.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00188.html
Andy Lester forwarded a patch last week to tidy up one-line loops, specifically, bringing the lone semi colon down to the next line and using a NOOP macro. Said macro can then be used to squirrel away the various comments that use secret handshakes to keep source analysis tools happy.
Rafael hated it. Nicholas Clark proposed a semantically equivalent alternative that met with the Andy seal of approval, and so Andy went back to refactor using the new approach.
It's overkill of course http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00102.html
He came back after a while with new versions of doio.c and dump.c and wanted to know what people thought of them. Rafael must have liked it, since he applied the patch.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00110.html
Along with a nice micro-optimisation for S_find_array_subscript.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00114.html
Andy then thought he could remove a goto in a section of code in op.c, since the only thing it does is jump over a single if block. The concept was perhaps sufficiently scary for no-one to dare apply it to see what would happen.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00119.html
Jarkko tweaked hv.c to use a safer approach to performing the task of zeroing out memory.
Know your macros http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00106.html
And cast his eyes upon pp_sys.c.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00107.html
And a tweak to shave some memory off the size of a microperl.
Smaller is better http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00117.html
Jarkko also added some enhancements to the PERL_MEM_LOG infrastructure, that allows very detailed logging of memory allocations. Jarkko hoped that someone would feel sufficiently inspired to write some code to munge the output and produce some pretty pictures to help gather a better understanding of allocation patterns.
Your name in lights http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00246.html
...by yours truly, and patches applied by Rafael.
Historians may find it of interest that the patch to context.t was the first ever since its inclusion, following a bug report from François Désarmenien nearly six years ago.
t/op/context.t http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00134.html t/op/grep.t http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00133.html t/op/list.t http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00138.html
And in other news, your summariser ran into a minor problem of resource acquisition (not enough semaphores available) to run a couple of tests in blead's suite, and set patches to fix that up as well.
ext/IPC/SysV/t/ipcsysv.t http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00230.html ext/IPC/SysV/t/sem.t http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00231.html
In doing so, another minor problem arose with fold_constants JMPENV_PUSH panics. Dave Mitchell sorted this out, but you'll have to wait for next week's exciting episode to find out how (this is due to a severe warp in the space-time continuum, in that the summary is really late this week).
That's not supposed to happen http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00220.html
The recent work done by Yves and Vadim blew away a couple of assumptions. Sadahiro Tomoyuki identified the source of the problem. A brief flurry of patches had it fixed up quickly.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00111.html
Another problem showed up, this time relating to threads.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00245.html
And a final one, where perl was built and yet managed to forget to link in a Perl_* function, because the export list for the linker had become messed up. Sorted out by Steve Hay and Nicholas Clark.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00273.html
A recent change to a ext/IO/t/io_unix.t to permit a fall-back to /tmp if socket creation fails in the current directory causes grief on AFS file systems. People tried to figure out how to work around this added twist. Mike Guy wondered it it wouldn't be easier to figure out first why the socket was failing in the current directory in the first place, then maybe people wouldn't have to deal with this new case.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00173.html
rcatline doesn't stringify references (#39037)and maybe it should http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-04/msg01103.html
pal@hp sent in some patches to make ExtUtils more robust in the face of super-fast hardware.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00128.html
readline the last line with no newline (#39060)Mark Martinec observed that when the last line of a file lacked a newline, he would observe Bad file descriptor errors, and supplied some code to show how to reproduce the problem
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00152.html
Data::Dumper and numeric scalars (#39062)Brad Baxter noticed that Data::Dumper would sometimes quote a scalar that would otherwise not need quotes, as it was numeric. Unfortunately, he wasn't able to pin the change in behaviour down any more accurately than between 5.6.1 and 5.8.7.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00153.html
This was a problem related to linking with -fpic as opposed to -fPIC. Debate raged over how to get it sorted out in Configure.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00156.html
A similar problem, for which the build infrastructure offers a couple of alternatives.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00157.html
When locales are in use, Perl doesn't sort the same way as the GNU sort program in Linux, nor PostgreSQL Sadahiro Tomoyuki explained that perl isn't making this stuff up as it goes along, merely using whatever C's strxfrm function cares to return.
So what are the others using? http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00242.html
Andreas Koenig showed how overloading "" and adding a dash of qr// into the mix can produce a core dump.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00247.html
$# treats 0 specially (#39097)Ruud Affijn showed what strange and wonderful things can happen when you embed a newline in the #$ variable. Which you shouldn't be doing anyway as its usage is deprecated after all. Andy Dougherty traced the behaviour all the way back to perl 1.010.
Good novelty value http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00281.html
Pod::Html error stops CPAN install/test of Pod::Readme (#39098)This bug highlighted the issue of what to do when installing a POD file as a man page, and the POD is malformed. Should the file be skipped? Should the installation be aborted?
Halt and Catch Fire http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00282.html
14 opened + 18 closed = 1523 http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00289.html
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00142.html
Peter Dintelmann followed up on the thread last week about length specifiers in unpack's mini-language and came up with a documentation patch, first for maint, and then for blead.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00168.html
Since ${^WIN32_SLOPPY_STAT} is in blead, Rafael called for some documentation, to explain what it does. Jan Dubois complied.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00090.html
By the same token, Jan also clarified hard link support on Windows.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00141.html
Mohammad Yaseen had some problems building Perl modules in non-standard locations. There was the usual chorus of advice about PREFIX and PERL5LIB but the really interesting news from the thread was that Randy W. Sims mentioned that Module::Build now (as in 0.28) supports ExtUtils::MakeMaker's PREFIX functionality.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00092.html
Things seemed to be moving along for Mohammad. After having successfully built perl on z/OS, he was having trouble dealing with the semantics of environment variables. Dominic Dunlop guided him through the minefield.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00118.html
Dominic requested more information about Perl on Windows 98. Even the original poster thought that it probably wasn't worth the effort to pursue any further.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00135.html
A few more data points on the issue of taint and fork on Win32, courtesy Perlmonks.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00178.html
Paul Johnson returned to Adam Kennedy's question about how to tell whether a file handle is seekable, as he had run into pretty much the same issue with IO::Compress:Zip. In the end he simply documented that trying to do X with Y just does not work.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00085.html
Shlomi Fish found a Heisenbug with perl -d. Dave Mitchell confirmed that it is fixed in blead. Andreas Koenig confirmed that it was fixed with a Heisenpatch.
Now you see it. Umm... http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00236.html
Ash Berlin spotted a couple of places in perlop.pod with incorrect L<...> markup.
Try writing the above sentence in POD yourself http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00249.html
Nicholas Clark discovered that GCC does not conform to the C standard, section 6.8.6.4. Marcus Holland-Moritz comforted him with the idea the Intel compiler gets it wrong too.
A void hate http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-05/msg00275.html
This summary was written by David Landgren. My humble apologies for the tardiness, Real Life kept me busy this week.
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:
http://www.landgren.net/perl/
Weekly summaries are published on http://use.perl.org/ and posted on a mailing list, (subscription: perl5-summary-subscribe@perl.org). The archive is at http://dev.perl.org/perl5/list-summaries/. Corrections and comments are welcome.
If you found this summary useful or enjoyable, please consider contributing to the Perl Foundation to help support the development of Perl.