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.
  • Re:my take on 5.6 (Score:1, Interesting)

    by the way (155) on 2000.05.28 8:30 (#192)
    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

    I agree with everything you said, except this... How does methods as lvalues through encapsulation out the window? I think the opposite--methods as lvalues allow you to change the interface anytime, as long as you ensure that your method ends up returning the thing you want changed.

    Having said that, I much prefer the Delphi way, where 'properties' have 'read' and 'write' methods (or field names). This is simple, and effective.

    Also, what's the improvements in pseudo-hashes you mentioned? They've been in Perl a while now--are they done differently in 5.6?