Yasuo Ohgaki <[EMAIL PROTECTED]> wrote: > I guess the original reason why PHP has case insensitive > class/function names is consistency with HTML standard. > If so, XHTML _is_ case sensitive, we should go for case > sensitive names.
although only rasmus can say for sure, i'd say you are assuming way more thought went into the original decision than actually did. case-insensitive function names are easier for developers. personally, i don't think any of the arguments for making function names case-sensitive hold water. (it also happens to allow a sidestepping of one of the coding standard battles -- studlyCaps or LeadingCaps or nocaps?) while i want to commend you for your cleverness in using the bug database voting system to collect opinions about this issue, i think it may be worth making clear that any such voting is not likely to be considered binding by anyone. (democracy is an extremely poor way to design software.) jim (who only has a passing relationship with his shift key, so who really cares what he thinks, anyway. :) -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
