in reply to Re: The costs of packages
in thread The costs of packages
Inheritance is not a requirement nor even desirable for my application. The types I am talking about are not really classes per se, just perl convenient wrappers around C-structures that will be passed to OS calls.
On a slightly related question while your around. Is there any reason beyond your personal preference for using create rather than new?
I've tried it both ways and it does exactly what I was achieving with my scheme, but without the overhead, which is great--thanks again--but I'm wondering if you know of some trap waiting for me if I use "new" as the constructor name?
Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham"When I'm working on a problem, I never think about beauty. I think only how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong." -Richard Buckminster Fuller
If I understand your problem, I can solve it! Of course, the same can be said for you.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: The costs of packages
by Abigail-II (Bishop) on Sep 17, 2003 at 00:23 UTC | |
Re3: The costs of packages
by dragonchild (Archbishop) on Sep 17, 2003 at 13:33 UTC | |
by BrowserUk (Patriarch) on Sep 17, 2003 at 17:26 UTC |
In Section
Seekers of Perl Wisdom