Re: PEAR2 standards: anything good at all?

Lukas Kahwe Smith wrote:

The difference is that users in this case will be "forced" to rely on PHP native functionality and that they can expect a clear error message. So I am not so worried, but of course we will still see our share of "__autoload() wtf" support requests.

I think you just hit on something there, Lukas. __autoload and include_path are both features that aren't going to be immediately apparent to the new user that this is supposed to help. You're trading one support/bug request for another... In any event, I see either of these proposed methods as a trade-off. __autoload() is going to be slow, allfiles is going to gobble up memory. From the discussion that I've seen and participated in, we have two camps here that are equally intractable. I seriously doubt any further discussion is going to sway any minds, so I would be for moving this to a vote (or whatever would start its end of life cycle) so the standard can be adopted and/or rejected and people can likewise move on to to the important task of following or ignoring it... ;-) -Travis