The evil part is, is that (for our system) the user-supplied query must be subclassed from a built-in base class, which is not delivered as PERL code to the end-user.
So? You're not supposed to know anything the base class is doing. As long as its interface is strict and well-documented, you won't have a problem. Unit testing should handle your problem.
Does anyone else think that it's pretty slick that a perlapp EXE can load on-disk perl modules
No, but I'm probably not the one to ask. I've gone through enough Perl golf that anything much less than a Schwartzian Transform doesn't impress me anymore.
----
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
In reply to Re: Win32 binary (and extensible) OO-perl applications
by hardburn
in thread Win32 binary (and extensible) OO-perl applications
by dpmott
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |