NOTE: Continuing from thread "Call it: allow reserved words in a class or not?":
As much as I'd love to see more case-sensitivity, I'm afraid it would
break quite a lot of existing apps, according to Google Code.http://www.google.com/codesearch?q=lang%3Aphp+%3D%5Cs%2AArray
-JD
It's worse than I thought, really out of the question for 5.x.
Though I still think it's something we should consider for 6.0 as it's something we need to fix in the long term (and 6.0 already has breaks, such as strings used in binary operations need to be changed to binary strings).
I can provide a short PHP script which can automatically fix the case of internal classes and keywords like array() in most source code out there.
We can test such automated porting scripts on samples collected from PEAR, Google Code and projects like Drupal, Joomla etc. to reduce side effects.
Regards, Stan Vassilev
NOTE: Continuing from thread "Call it: allow reserved words in a
class or not?":As much as I'd love to see more case-sensitivity, I'm afraid it would
break quite a lot of existing apps, according to Google Code.http://www.google.com/codesearch?q=lang%3Aphp+%3D%5Cs%2AArray
-JD
It's worse than I thought, really out of the question for 5.x.
Though I still think it's something we should consider for 6.0 as
it's something we need to fix in the long term (and 6.0 already has
breaks, such as strings used in binary operations need to be changed
to binary strings).I can provide a short PHP script which can automatically fix the
case of internal classes and keywords like array() in most source
code out there.We can test such automated porting scripts on samples collected from
PEAR, Google Code and projects like Drupal, Joomla etc. to reduce
side effects.
NO!
regards,
Lukas Kahwe Smith
mls@pooteeweet.org
Lukas Kahwe Smith wrote:
NOTE: Continuing from thread "Call it: allow reserved words in a class
or not?":As much as I'd love to see more case-sensitivity, I'm afraid it would
break quite a lot of existing apps, according to Google Code.http://www.google.com/codesearch?q=lang%3Aphp+%3D%5Cs%2AArray
-JD
It's worse than I thought, really out of the question for 5.x.
Though I still think it's something we should consider for 6.0 as it's
something we need to fix in the long term (and 6.0 already has breaks,
such as strings used in binary operations need to be changed to binary
strings).I can provide a short PHP script which can automatically fix the case
of internal classes and keywords like array() in most source code out
there.We can test such automated porting scripts on samples collected from
PEAR, Google Code and projects like Drupal, Joomla etc. to reduce side
effects.NO!
Is that to any move to case sensitivity? Even if it is the tidiest way of
plugging some of the holes in a clean UTF8 implementation via 6.0 where
'lower' or 'upper' may produce different results?
Personally I've always worked with maintaining case - C++ dictates it - so
it's natural to ensure that a case-sensitive search always provides the
correct results. I'll even correct code that differs ....
--
Lester Caine - G8HFL
Contact - http://lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php