Am 05.06.2017 um 10:14 schrieb Tony Marston:
wrote in message news:3cfc0130-e530-64ed-36e8-372b04481...@rhsoft.net...
Am 04.06.2017 um 11:10 schrieb Tony Marston:
If there was never a standard to begin with then there should be
proper justification for introducing one now, and I'm afraid that "to
be consistent" is not a valid argument. What problems are caused by
this inconsistency? What is the cost, both in core developer time and
application developer time, to change it? If the benefits are smaller
than the costs then can the change actually be justified?
seriously, if you don't understand the obvious benefits of consistency
when a lot of different people have to deal with source code over a
long period of time likely the discussion with you is pointless and
just wasted time for everybody involved
Seriously, can you explain in words of one syllable the precise benefits
of such a consistency? Can you measure the benefits? Just because some
OCD sufferers like consistency is not a good enough reason. I have been
programming for over 30 years, and in that time I have had to deal with
both snake_case and CamelCase, and while I personally find that
snake_case is more readable, especially with names that contain more
than 3 or 4 words, I have no trouble reading either. Having a mixture of
styles does not cause a problem (except in the minds of OCD sufferers)
so IMHO it does not require a solution. Anybody who says that they
cannot work with a mixture of naming styles is either a liar or Illiterate
it feels like talking with a blind guy about colors
who said "cannot"?
i can mess up my living room and life still goes on
but i won't
i can live without taking a shower over weeks
but i won't
i could work with someone which has a terrible coding style
but i won't
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
