You are here: Re: Breaking backwards compatibility - good or bad? « PHP Programming Language « IT news, forums, messages
Re: Breaking backwards compatibility - good or bad?

Posted by Jerry Stuckle on 01/01/06 00:14

Colin Fine wrote:
> Jerry Stuckle wrote:
>
>>
>> Neither I nor anyone else needs to "give a convincing reason...". The
>> bottom line is - that's the way things are, and it is supported by a
>> vast majority of programmers.
>>
> How's that again?
>
> So "because most people like it that way" is a valid philosophical
> argument?
>

When the vast majority of programmers support the same philosophy, yes.

> I'm not expecting, or suggesting, that case sensitivity is going to
> disappear. But that has no bearing at all on whether or not it is a
> thoroughly bad idea.
>
>> However, there have been other reasons mentioned in this topic. But I
>> suspect none of them are "good enough" for you.
>>
> Really? The only reasons I can find in the trail (apart from the appeal
> to the majority*, and the scurrilous insinuation that case insensitive
> is somehow of the past and therefore worthless) are a barely relevant
> point from physics and a specific operational issue in PHP (which is in
> any case dependent on case sensitivity in the OS).
>

You should read again.

> * Did the majority ever vote on the topic? And don't say they did so by
> choosing C/Java/Perl: any of these could have been made case insensitive
> and there would have been essentially no difference; but they weren't
> offered.
>

But that's exactly how they voted. They used the language. If they
wouldn't have liked case sensitivity, they didn't have to use the language.

And don't give me any "They had to because their boss made them" crap.

C++ followed C in its case sensitivity. However, Java, PHP, etc. didn't
need to be case sensitive. They are because the original developers of
these languages saw the advantages and popularity of other case
sensitive languages.

>> And I haven't heard any good reasons why NOT to welcome it. Just
>> saying $Foo and $fOO shouldn't point to different variables doesn't
>> make it. To me they ARE different variables (although I wouldn't do
>> this myself).
>>
> The argument is that to people (you remember people? the things that
> write programs) 'project', 'Project' and 'PROJECT' *are* the same thing,
> and we all have to learn that we must always make a new distinction
> (which you have yet to demonstrate is useful) when we program.
>

Not to computers they aren't. And when I'm programming, they aren't the
same thing to me at all.

> Colin

Here's a suggestion. Don't try to argue your philosophy in this
newsgroup. You can't win, and it just shows how stubborn, old fashioned
or just plain out of date you really are.

Don't like PHP's case sensitivity? DON'T USE IT!


--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

 

Navigation:

[Reply to this message]


Удаленная работа для программистов  •  Как заработать на Google AdSense  •  England, UK  •  статьи на английском  •  PHP MySQL CMS Apache Oscommerce  •  Online Business Knowledge Base  •  DVD MP3 AVI MP4 players codecs conversion help
Home  •  Search  •  Site Map  •  Set as Homepage  •  Add to Favourites

Copyright © 2005-2006 Powered by Custom PHP Programming

Сайт изготовлен в Студии Валентина Петручека
изготовление и поддержка веб-сайтов, разработка программного обеспечения, поисковая оптимизация