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.
  • by Matts (1087) on 2001.12.11 6:00 (#2240) Journal
    I think you *do* like object oriented code. You just don't like the syntax.

    Moreover, I think you might like it better if you thought in terms of message passing. You pass an object a message to frobnosticate, and it obeys.

    Besides, not everything should look OO, it's just a good design pattern for the underlying system. Read the internals section of the pickaxe book and you'll see what I mean - I'm willing to bet it would be impossible to explain Perl's internals in such a short section.

    But we should still be pragmatic. Yes, a + b should still look like a + b. It just makes sense that way. How it's implemented internally though is of consistency and beauty (in ruby's case).

    Besides, processors work procedurally, not OO (well, these days they do funky parallel stuff, but I digress), so it would be impossible to be procedural all the way down to the bare metal. It's just a useful tool to layer over procedural code.