Paolo Campanella wrote: > > Paolo Campanella wrote: > > > The 'split' must have crept in as one of a bunch of experiments I tried > > to nail down the problem, and forgot to remove - very un-fun :-( > > Correction: the problem is only visible when using $/=undef and > splitting on newlines, as per my original post. When using the list > context, everything works as one would expect. Sounds like you have uncovered a bug with the /proc file system. Have you explored the exact system calls, or at least mentioned this difficulty to a kernel developer? Which kernel are you using, for instance, and does the behavior go away on a different kernel? Then again it could be perl; how does undefined-delimiter slurping work exactly? There is no "read until eof" system call, all the system calls take some kind of length argument. When you read the length of this /proc pseudo-file at a system call level, do you get the length of 63 of its records? If that is the case, whose problem is it? The moral for now seems to be, "Don't use undefined slurps to read /proc pseudo-files" __________________________________________________________________ David Nicol 816.235.1187 nicold@umkc.edu echo "Guns don't kill people, people using guns kill people"|perl\ -pe 's/guns/mirroring software/gi; s/kill people/commit piracy/g' ==== Want to unsubscribe from Fun With Perl? Well, if you insist... ==== Send email to <fwp-request@technofile.org> with message _body_ ==== unsubscribe