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

use Perl Log In

Log In

[ Create a new account ]

runrig (3385)

runrig
  dougwNO@SPAMcpan.org

Just another perl hacker somewhere near Disneyland

I have this homenode [perlmonks.org] of little consequence on Perl Monks [perlmonks.org] that you probably have no interest in whatsoever.

I also have some modules [cpan.org] on CPAN [cpan.org] some of which are marginally [cpan.org] more [cpan.org] useful [cpan.org] than others.

Journal of runrig (3385)

Thursday April 24, 2003
06:01 PM

new Object

[ #11833 ]
Re: Simon Cozens' latest log entry, just one more reason I never ever say new Object (@args), but always Object->new(@args) (in perl, that is). I just don't want to ever worry about having one of those hair-pulling what went wrong sessions. Not that they don't happen for some other reason :-)
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.
  • When I had my upcoming Alpaca book in review, more than one person took me to task for berating indirect-object notation, including claims that "they've never been burned by it, so go easy". Too bad. I stood my ground. And that's the way it'll appear.

    At least the readers who read the logical sequel to the Llama book will get the right kick in the pants.

    If Simon can get bit by it, so can everyone. Heck, I even got bit by it while developing the object courseware (see perlboot [perldoc.com]).

    --
    • Randal L. Schwartz
    • Stonehenge
  • I've had people complain about every damned thing in my book [amazon.com], but so far no critiques about the appendix which explained OOP and where I explicity try to steer people away from IObj syntax. This surprised me.