Stas Bekman wrote:
finfo() from Apache::compat collides with the new $r->finfo implementation, the two can't coexist...
this is actually a problem with more than just $r->finfo - in places where the method is redefined and the new one takes different arguments than the old, right?
Different arguments but also the same number of them or none, yes. If the number of arguments is different we can code around it in compat. But the problem with $r->finfo is that it breaks the smoking, whereas others aren't (I think other aren't exercised in both forms)
Solutions?
I have no idea. I'm not inclined to change anything in 2.0 core just because the compat layer has issues - presumably, things are "right" in core (finfo and otherwise).
the easiest fix would be to disable finfo from compat, which I'd be ok with since finfo wasn't really all that popular anyway (unfortunately).
Disabling is imperfect, since the new code is way too different. May be renaming finfo to finfo_old in compat.pm, so that at least it'll be easier to do the initial transition by just adjusting only one bit and not many. In fact that what I think we should do for all functions in compat.pm that collide. What do you think? May be we should ask the users?
__________________________________________________________________ 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]
