Geoffrey Young wrote:May be we should open up this question for more people?2) liz, your opinion here is especially valuable wrt what is "intuitive." stas and I both have our own (generally differing) opinion of API intuitiveness, and as someone who is in the middle of figuring out the new API, you represent a good test case. of course, if we don't agree with your opinion, well... ;)
Please do. I don't think I can qualify as a "user" in that respect. Yes, I have used mod_perl from almost the very beginning, but there has been a "hole" in my experience from say 1999 through 2002...
There are quite a few folks who have moved to mp2 or in the process of doing so and certainly will have things to say. I'd suggest to ask for their input of what people have found hard and whether we need to change things before 2.0 is cast in stone.
Certainly we aren't oblidged to follow all the suggestions, but it's a good idea to hear what users have to say.
What I really find annoying, is that when you're porting, things start to fail. I realize (now) that there is a way to find out which method resides in which module:
http://perl.apache.org/docs/2.0/user/porting/porting.html#Using_C_ModPerl__MethodLookup__to_Discover_Which_mod_perl_2_0_Modules_Need_to_Be_Loaded
but why does this have to be done manually? Why can't there be an AUTOLOAD sub that _by default_ puts a warning in the error log, loads the right module and just makes the right sub gets called?
Liz
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
