in reply to How about class Foo {...} definition for Perl?
I feel about this the same way I feel about all auto-generated class modules: if you already understand OO Perl and you happen to like the module in question, then go ahead and use it. Just as importantly, you should know the limits of the module so you know when to ditch it (just like any other tool). Personally, I would avoid Class::HPLOO simply because it relies on source filtering, which is always messy. If you can come up with a non-filtering solution with reasonable performance, I might use it.
----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer
: () { :|:& };:
Note: All code is untested, unless otherwise stated
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: How about class Foo {...} definition for Perl?
by gmpassos (Priest) on Jan 18, 2004 at 02:13 UTC | |
by hardburn (Abbot) on Jan 18, 2004 at 14:14 UTC |