Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical
 
PerlMonks  

Re: OOP's setter/getter method - is there a way to avoid them?

by sundialsvc4 (Abbot)
on Oct 27, 2015 at 15:34 UTC ( [id://1146125]=note: print w/replies, xml ) Need Help??


in reply to OOP's setter/getter method - is there a way to avoid them?

This node falls below the community's threshold of quality. You may see it by logging in.

Replies are listed 'Best First'.
Re^2: OOP's setter/getter method - is there a way to avoid them?
by Your Mother (Archbishop) on Oct 27, 2015 at 16:40 UTC

    My eyes get blurry at this point. Without deeper qualifications almost everything you said is false. Picking two easy ones.

    including the unprecedented system, Moose

    I alluded to this before when you went on a Perl6 bashing rant while singing the praises of Moose—from the Moose docs: Moose is based in large part on the Perl 6 object system, as well as drawing on the best ideas from CLOS, Smalltalk, and many other languages.

    You might assume that something as “radically different” as Moose et al would carry with it a hefty performance price ... but it doesn’t.

    Of course it does. Moose is about 1,000% slower than straight hashrefs, 750% slower than plain objects, and there are sweetened syntax/utility options like Object::Tiny::XS and Mouse::XS that are still much faster than Moose. But again, without qualification for what use, what place, etc, all such speed statements are noise.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1146125]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others sharing their wisdom with the Monastery: (6)
As of 2024-04-23 14:25 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found