Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • my take on 5.6 (Score:1, Interesting)

    by orabidoo (111) <see@my.webpage> on 2000.04.20 7:11 (#153) Homepage
    looking at the main new features of perl 5.6:
    • unicode support: it's a good thing, and not intrusive: it's off unless I "use utf8".
    • lvalue subs: not really important; I can see it being used in methods, i.e allowing $object->method = $value, rather than the usual $object->method("value"). OTOH, that throws encapsulation out the window.
    • improved threading, and win32 fork emulation. I dislike both threads and win32, so no comment. If peopel find it useful, it's good, I just hope it doesn't bloat perl too much when i'm not using it.
    • improved perl compiler: neat, I wish it got to the point where it's usable in practice, though. bytecode production and loading seems to be 'almost there'; I'm looking forward to them.
    • auto-vivification of filehandles: great. finally say goodbye to the Symbol::gensym kludge, for those cases where IO::* is just too heavy.
    • weak references: neat idea, annoying implementation. I mean, it needs support in the core anyway (to turn dangling weak refs into undef at free time), so why not just make it part of core and have a 'weaken' func, instead of needing a special module?
    • delete/exists on arrays: neat.
    • lexical warnings: cool.
    • 'our': I still think 'use vars' was perfectly good enough, and this is just added confusion.
    • v1.3.6 strings: kind of worthless.
    • large (>2GB) file support: good feature.
    • improvements in 'use fields', typed object refs and pseudo-hashes: the idea is to make objects look like hashes (with fields in $obj->{keys}), but be actually implemented as (faster) arrays, with compile-time checking of what field names actually exist. I'll be using this.