Stas Bekman <[EMAIL PROTECTED]> [19-11-2004 21:51]:
Radoslaw Zielinski wrote:
Stas Bekman <[EMAIL PROTECTED]> [14-11-2004 17:05]:
Radoslaw Zielinski wrote:
[...]
to support this aliasing feature. Or do you suggest to just alias the namespaces?
Maybe I'm missing something. I was thinking about just aliasing the namespaces.
It's a way more complicated than it seems to be at first sight. Search the dev list's archives for EazyLife to see some of the problems.
Done... OK, so AUTOLOAD is just a can of worms. But, as the code we're trying to make work already knows which modules does it need to work, we can try a different approach: trap the "use Apache::OldName" calls with a subroutine ref in @INC. Example implementation attached; would this work? I actually don't really like it, as it's a hack, but... I can't see how this could impact on anything. Well, let's see what I've missed now ;-)
IMHO, it's a waste of time to try to resolve the namespace issue before the API incompability is resolved (which I doubt is possible or shouldn't be even attempted)
Huh? Resolving the namespace issue just removes the API incompatibility problem, doesn't it?
How so? IMHO, it's totally unrelated. If you have a function foo() which under both versions accepts the same amount of arguments, which are totally different, and does a completely different thing and returns different things as explained here:
http://perl.apache.org/docs/2.0/api/Apache/compat.html#Compatibility_Functions_Colliding_with_mod_perl_2_0_API
how resolving the namespace issue is going to resolve that issue?
Have you read the URL quoted above? The two APIs behave totally different
Yes, Stas, I have read it. Several times, actually, to make sure I haven't left out any unresolvable issues. I really don't see any. Could you name it?
Great. So do we agree that there is an issue which is a showstopper for the rest of the suggestion? (see above)
Moreover there are APIs which don't exist anymore and for some of them it's not possible to implement for backword compatibility.
and it's not possible to figure out at run time, which API generation is desired.
...I just don't see an easy way to resolve this one right now, if the httpd.conf directive option I mentioned earlier is not acceptable / possible. But I think I'll figure something out.
sorry, Radoslaw, I'm not sure which directive are you talking about. could you please quote the relevant part of your suggestoin?
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
