in reply to Re: DWIM: autoloading classes in thread DWIM: autoloading classes
While I'm too tired to implement it, one should be able to add import functionality to the above code so that symbols exported by Foo::Bar via "use Foo 'Bar';" are exported to the calling namespace. That should be doable by testing whether Foo::Bar uses Exporter to handle import() and friends and use the export_to_level() routine from Exporter. If the module uses its own import routine, one might... well... do evil things with eval and package.
Re: Re: Re: DWIM: autoloading classes
by liz (Monsignor) on Sep 18, 2003 at 07:00 UTC
|
Not that I want to export anything: I do everything OO and nothing gets exported in my modules. If there are any global flags that would need to be set, I use class method accessors for them.
But anyway, but I fail to see what more evil things you could do with an exporter that you couldn't already do.
So what ev(i|a)l things exactly are you referring to?
Liz | [reply] |
|
| [reply] |
|