Tuesday, March 23, 2004, 8:32:51 PM, you wrote: >> Is this really the criteria being used to support a lack of consistency? >> >> This sort of thing (inconsistency) is one reason why PHP is frequently >> attacked and why developers consider various APIs to be unintuitive. We >> should pick a standard, any standard, and stick to it. I dislike >> StudlyCaps as much as the next guy, but I think inconsistency is even >> worse. >> >> I thought this issue was decided a few months ago... >> >> Chris
> I really hate the Studlycaps convention. I prefer the old dash. > Why not use this only for new extensions? Do you know the pain to update all > the docs??... > You have changed Tidy and SQLite so far. Thats lots of work for me and for > the documentation team. Nuno: I can believe and i am thankfull you did the work :-)) > I would vote to use that convention just for new extensions. RC1 is out and > the persons are already testing and trying out their scripts. Why make a > script that worked in RC1 incopatible with RC2? > And I would vote even to revert the changed in Tidy and SQLite... Who > prefers the Studly caps instead of the well used '_'? To the list: From my perspective it seems we were to fast with RC1. I am still coding and fixing deep internal things and even in the middle of releasing RC1 we had to change features which affect much more ppl than mysqli's oo api which more or less noone uses so far (it was and is still a moving target). As a consequence i forgot to change SQLite's OO API earlier and to reming georg again of that issue - sorry for the inconvenience. For me one thing counts consistency. And don't tell me that it is problematic for our users to transliterate from dashed_names to studlyCaps. It is work for us (for example it took me like about two hours: coding, testing and discussing) but the result is bit ease of use for our users. best regards marcus
