Don't ask to ask, just ask | |
PerlMonks |
Re: AUTOLOAD - the good, the bad, and the uglyby raptnor2 (Beadle) |
on Oct 15, 2004 at 02:56 UTC ( [id://399383]=note: print w/replies, xml ) | Need Help?? |
I've used it to wrap classes that I wouldn't know anything about, but needed to provide add-on methods for component management. Using this technique, I don't have to care what someone wants to use as a component (as long as it's a class). A snippet from IOC::Lite follows:
I've taken the concept a little further, almost AOP like, in the version of IOC::Lite I'm working on now. That way I can add all types of features to objects the container doesn't own. The basic component management methods will be first, followed closely by dynamic logging. Not sure where I'll head from there. Sorry if this is just rambling. Bottom line: I think it would be quite useful on large software projects. I can't tell you how many times I wished I had this feature when coding in (C/C++/Java/etc)
Cheers, John
janitored by ybiC: Replace frowned-upon <pre> tags with Monastery-standard <code> tags
In Section
Meditations
|
|