Stas Bekman wrote:
Now that ModPerl::MethodLookup handles mp1 methods as well, I've decided to put together a package that will further assist the porting process. All the needed bits are there already, this package just makes things a bit easier to setup.
Notice that its purpose is to assist the porting process, not provide the backcompatibility layer, so it dies every time it has to say something.
I'm considering to put it into the core, next to Apache/compat.pm.
this is a nice idea. go ahead and put it in.
I'm also trying to handle the mp1 core packages that are no longer exist, by overriding CORE::require, but I'm stuck at not being able to do 'goto &CORE::require', since in pure perl you can't reference core functions (at least I couldn't figure out how to do that) :( Any idea how to resolve that?
personally, I'm less and less convinced that compat.pm is a good idea. as mp2 gets more mature, everybody is starting to find that it has problems, the biggest being that if you use (or any modules that relies on it uses it) it you can't use the mp2 api anymore. so, what we're largely seeing is modules skipping compat and porting their code to the new api (AuthCookie comes to mind).
whether you agree with this assessment or not, you mentioned working on more pressing issues :) in my mind, compat.pm is at the bottom of the list, since it probably won't end up working out anyway, or by the time we make it work people will have figured out the new api and it will be a non-issue.
--Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
