P is for Practical | |
PerlMonks |
Re^3: Altering Package Subs and Running In To Problemsby Aighearach (Initiate) |
on Nov 11, 2004 at 08:20 UTC ( [id://406950]=note: print w/replies, xml ) | Need Help?? |
Unfortunately, internals means picking a good C book, and setting down with the perl source code. There are also lots of good online resources. YMMV As far as, turning the OO world on it's head, from what I can tell your system is just really brittle, and steps on everybody's toes. What about your system differentiates and improves on subclassing? Can you give a realworld example where your system makes plugins easier than subclassing? I use a custom plugin system for my web template system (because Mason lags), I just define a simple interface and then plugins just have to implement a handler(). I thought about making them just run without forcing them to define their own package names, etc, but then it just gets harder to tell which is which when I'm looking at the performance times. That is, doing it the "right" way, I can track stats based on package names. Would your system help me? -- Snazzy tagline here
In Section
Seekers of Perl Wisdom
|
|