[jifty-devel] Classloader's loader
nelhage at bestpractical.com
Fri Jan 5 16:51:45 EST 2007
After unrelated poking yesterday, we discovered that the fix actually
doesn't do anything. Did the problem go away for unrelated reasons, or
what's the current status?
I'm still a little fuzzy on what the actual problem was, so I'm not sure
what to investigate.
I suspect, though, that the clean solution is to just pass require => 0
to M::P, and then just require all the modules ourselves with
Jifty::Util->require. Is there some reason that doesn't work?
On Wed, Oct 25, 2006 at 08:25:10PM -0700, Jesse Vincent wrote:
> On Oct 25, 2006, at 11:28 AM, Gaal Yahas wrote:
> >On Wed, Oct 25, 2006 at 09:36:12AM -0700, Jesse Vincent wrote:
> >>>Alternatively, we could simply subclass Module::Pluggable and
> >>>override its require() with the above sub(). This has the
> >>>distinct advantage of not messing with the namespaces
> >>>directly (but it is the moral equivalent).
> >>Yep. And talking to Simon (Author of M::P), that's the recommended
> >>path. Wanna give it a shot?
> >(Sorry, my tuits have been commandeered.)
> I've just rolled a fix for this (I hope) into jifty-trunk. You up for
> seeing if I made it better at least? ;)
> jifty-devel mailing list
> jifty-devel at lists.jifty.org
More information about the jifty-devel