On Wed, 2002-02-06 at 22:36, Jani Taskinen wrote:
Many scripts will break anyway if you update to PHP 5..
+1 (still) for case-sensitivity which would make the language
more conistent. Or if this is ruled out, then let's make all
variables and constants case-insensitive too. It is so
Yasuo Ohgaki wrote:
Case of names can be easily converted by program.
do you think it will be easy in this situation?:
?php
function myCompare($arg1,$arg2) {
}
[...]
$sorted_array=usort($array,myCompare);
[...]
$sorted_array=usort($array,mycompare);
[...]
?
and, by the way: what kind of a
At 07:58 AM 2/7/2002 +0100, Stig S. Bakken wrote:
After careful consideration on the CS issue I must say I agree with John
here. The _only_ case where I feel CS is a problem, is when dealing
with other environments. But the price for changing this today is
simply too high. It should have been
Andi Gutmans wrote:
At 07:58 AM 2/7/2002 +0100, Stig S. Bakken wrote:
*SNIP*
I agree and I'll try and check if pretty names can be handled.
Errors with case senstive names are intuitive to fix.
While errors with name space change is _not_ intuitive
to where and what is wrong.
If we didn't
Hi all,
I'm posting this for those who are not subscribing
Zend Engine 2 list.
Many of developers seems to have case sensitivity for
class/function names.
However, we need vote for if PHP5 will have case
sensitive class/function/constant names.
If you have comments, please submit one.
PS: We
However, we need vote for if PHP5 will have case
sensitive class/function/constant names.
+1 for case-sensitive everything
Cheerio, Marc.
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
However, we need vote for if PHP5 will have case
sensitive class/function/constant names.
+1 for case-sensitive everything
-1. Differentiating two objects only by the case of their names
seems absurd to me. This is not how humans function.
Ease of implementation is the only thing speaking
oci and gd extensions had mixed-case names for ages,
but you see both mixed- and all-lower case usage
all over the place now
OK, I see your point.
I'll start writing a little shellscript that recursively crawls through your
filesystem, updating every text-file against a list of
Marc wrote:
I don't think people should write code that differentiates by case, but
case-sensitive coding leads to consistency in naming, so you will not read
MySQL_ConneCt somewhere and mysql_connect somewhere else, while it means the
same thing...
If you just want to promote case-accurate
On Wed, Feb 06, 2002 at 07:40:18PM +0900, Yasuo Ohgaki wrote:
Hi all,
I'm posting this for those who are not subscribing
Zend Engine 2 list.
Many of developers seems to have case sensitivity for
class/function names.
However, we need vote for if PHP5 will have case
sensitive
On Wed, 6 Feb 2002, Brent R. Matzelle wrote:
--- Marko Karppinen [EMAIL PROTECTED] wrote:
However, we need vote for if PHP5 will have case
sensitive class/function/constant names.
+1 for case-sensitive everything
-1. Differentiating two objects only by the case of their
Thanks for posting this request for comments, Yasuo.
I think from a C developer's point of view, it makes perfect
sense to have case-sensitivity. From a scripting point-of-view,
I think it is a step backward. Studies by the Python group
have shown that case-sensitivity is a serious barrier for
Title: RE: [PHP-DEV] [Fwd: Re: [Zend Engine 2] Case sensitivity: Conclusion(?)]
Thies C. Arntzen writes:
On Wed, Feb 06, 2002 at 07:40:18PM +0900, Yasuo Ohgaki wrote:
Hi all,
I'm posting this for those who are not subscribing
Zend Engine 2 list.
Many of developers seems
I very much agree with this Email and am -1.
Andi
At 11:01 PM 2/6/2002 +0800, John Lim wrote:
Thanks for posting this request for comments, Yasuo.
I think from a C developer's point of view, it makes perfect
sense to have case-sensitivity. From a scripting point-of-view,
I think it is a step
Hi,
IMHO making PHP case sensitive after being case-INsensitive for so many
years is a very bad idea. The reasons are already mentioned on the list. For
us (ISP in The Netherlands) the most important one is BC. We would not be
able to upgrade any of our servers when this would go into PHP5. A
Many scripts will break anyway if you update to PHP 5..
+1 (still) for case-sensitivity which would make the language
more conistent. Or if this is ruled out, then let's make all
variables and constants case-insensitive too. It is so confusing
for all the newbies when $FOO isn't same as $foo.
On Wed, 2002-02-06 at 05:37, Marko Karppinen wrote:
Markus:
You have the wrong book then. Painless integration with other
technologies is the main argument (.NET, SOAP, SRM [didn't
forget it this time, Derick ;)])
I have some trouble believing that this is a real-world problem.
On Wed, 2002-02-06 at 10:13, Zeev Suraski wrote:
While I agree with Marko's vote (I'm also very much against it), I derive
my conclusion from a whole different perspective.
Guys, we are not next to the drawing board right now. The specs were
defined and the layout was laid years ago.
+1 for case sensitivity
On Wed, 2002-02-06 at 15:36, Jani Taskinen wrote:
Many scripts will break anyway if you update to PHP 5..
+1 (still) for case-sensitivity which would make the language
more conistent. Or if this is ruled out, then let's make all
variables and constants
No need to vote, it won't change anyways :)
Derick
On 6 Feb 2002, Jason Greene wrote:
+1 for case sensitivity
On Wed, 2002-02-06 at 15:36, Jani Taskinen wrote:
Many scripts will break anyway if you update to PHP 5..
+1 (still) for case-sensitivity which would make the language
20 matches
Mail list logo
