<not a flame>
Hey! Some of us out here LIKE case-sensitive languages. Is there really
any reason why you need to use STRPOS() in one place, StrPos() in another,
Strpos() in another, and strpos() in another? If you use any sort of naming
convention, the case-sensitivity actually HELPS people understand your code.
Get used to it, even html is going to end up being case sensitive when xhtml
becomes the day-to-day standard.
</not a flame>
- Theo
-----Original Message-----
From: Greg Brunet [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 10, 2001 1:05 AM
To: [EMAIL PROTECTED]
Subject: Re: [PHP-WIN] anti-advocacy: Larry Seltzer, pcmag May'01 pub.
Tim:
AAARRRGGH! They got it half-right with case insensitive functions and now
they're going to mess up the part that's done right!?! It is quite annoying
that they aren't consistent, but I was thankful that at least the functions
were working "right".
-- Greg
"Tim Uckun" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> From what I hear it's about to get worse. Instead of making variable
names
> case insensitive they are going to make the function names case sensitive
> too. Seems like they want to make the language more C like.
> As for other stuff my pet peeve is the lack of consistency in the
> functions.
<clip>
--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
