Re: Breaking backwards compatibility - good or bad?
Available news archives: comp.lang.tcl - comp.lang.python - comp.security.firewalls - sci.crypt - comp.lang.php - comp.lang.javascript
Google
 
Web news.hping.org


comp.lang.php archive

Re: Breaking backwards compatibility - good or bad?

From: Tony Marston <tony@NOSPAM.demon.co.uk>
Date: Mon Dec 26 2005 - 11:33:40 CET




"Anonymous" <anonymous@nowhere.invalid> wrote in message 


news:43AE8ECF.54D24C7C@nowhere.invalid...


> Tony Marston wrote:


>>


>> Case-sensitivity is the whole point of this thread. Any language that has 


>> a


>> feature which can be abused and which produces unmaintainable code is a 


>> BAD


>> language. Any language that allows the same variable or function name to


>


> Then any language is bad by your definition.



Any language that allows stupid mistakes is a bad language. That's why some 


programmers say that statically-typed and compiled languages are better that 


dynamically-typed interpretted languages.



> That's not true. Anyone proficient in german can assure you that "Helft


> den armen Vögeln." and "Helft den Armen vögeln." means something


> *completely* different! ;-)



Trust the bloody square-head sausage-eaters to throw a spanner in the works. 


But in ENGLISH, which is the universal language, there is no difference. 


Just check out any dictionary. Does it have separate entries in each case? 


No? I wonder why.....


Received on Tue Jan  3 03:44:31 2006