|
|
Posted by Kevin Andreoli on 12/17/75 11:54
On Tue, 1 Aug 2006 09:58:50 +0100, in article <ean53g$rlk$3$8300dec7@news.demon.co.uk>, I
saw that Tony Marston wrote...
|
|I prefer the PHP way. I have no problem with using foo, $foo, foo() and
|$object->foo() to differentiate between constants, variables, functions and
|methods. In fact the language which I used for 12 years before PHP used
|$$foo for global variables and $foo$ for local variables. The fact that it
|involves typing in a few more characters is totally irrelevant. It makes it
|easy to read, and it is much more important that code be readable by humans
|than by a computer.
|
|
Having read all of this thread so far, I feel it is time to add my twopennyworth. (Two
Cents for those across the pond.)
After 30+ years of writing code (never COBOL thankfully) I was, until recently, anti
case-insensitivity. Now I find I don't care much as I just follow conventions as
required by my employer's coding standards.
What I do care about, and have always rejected in anyone who works/worked for/with me is
the idea that ANYONE would use the same name for different entities in the same program.
Anyone who used foo, $foo, foo() etc. or ThisTHING thisthing ... in a program would be
reeducated quickly, using any necessary size of clue-stick. No matter what the case
convention I would NEVER expect to see two entities using the same name!
Whilst I like PHP I much prefer languages which expect all variables, constants etc. to
be declared before use. The addition of IMPLICT NONE to FORTRAN was a great leap forward
in that language's development.
--
Kev
NNNN
Navigation:
[Reply to this message]
|