[EMAIL PROTECTED] writes:
> On Wed, May 23, 2001 at 01:27:18AM +0200, [EMAIL PROTECTED] wrote:
>
> > All function names in the docs should be lowercase for consistence. No
> > matter where in the sentence, or how unreadable the function will be.
>
> I'm against this. It would result in unreadable and bad to
> remember function names.
>
> > For unreadable func-names, a longer-term renaming would be nice. But
> > first, get the manual lowercase. Then those php.dev guys will just need
> > to rename, because we are NOT going to write it mixed case anymore
> > for readability.
>
> I would recommend to make aliases in the source code first. After that we
> should the change the function names in the manuals.
>
> > Just only react if you strongly disagree. If nobody strongly disagrees,
> > I'll commit the changes somewhere in the next week. Thanks to Torben's
> > script, and including the <refentry> stuff etc.
>
> I have nothing against Torben, he has also read about my fight with some
> core developers and now the mysql_*() functions are more readable. You can
> also use the old syntax. The original functions havent been removed yet.
>
> -Egon
All of what Egon just said is why I didn't go through everything and
do this--it needs to be thought out better. For the Hyperwave
extension lowercasing didn't really affect readability, but for others
it could.
We've lasted this long with the manual being as it is, and as there is
an effort underway to figure out a standard naming scheme for PHP
functions, we should IMHO wait for that to happen before making
massive changes that could negatively affect readability in the
manual. A stylesheet solution would, until the naming scheme is
implemented, give us both a) the readability we have, and b) the
hyperlinking we want.
--
Torben Wilson <[EMAIL PROTECTED]>
http://www.thebuttlesschaps.com
+1.604.709.0506
