Re: variable names for different fortrans
- From: "PJH" <abc@xxxxxxxxxxx>
- Date: Mon, 19 Mar 2007 14:43:14 -0000
Beliavsky wrote
Camel case is better supported by a compiler if it warns about
inconsistent capitalization.
Do any Fortran compilers provide a warning?
I separate words within variable names using the underscore.
That looks a bit too much like the way other languages identify constants.
For that reason I tend to avoid it in Fortran (except for constants). Not
that we should be tied to other language conventions, of course. Its just
that I regularly use 4 different languages and having some commonality
between my source code helps moving between them.
Having said that, when I write Delphi or VB I use type identifier prefixes,
but somehow this never looks right in Fortran (there aren't enough standard
types to make it justified). My only concession to this is using "i" or "n"
for all integers and "j" and "m" for some integer dummy arguments in API
procedures (if I have to do type coercion).
Paul Holden
.
- Follow-Ups:
- Re: variable names for different fortrans
- From: Ben Hetland
- Re: variable names for different fortrans
- References:
- variable names for different fortrans
- From: allelopath
- Re: variable names for different fortrans
- From: Richard Harter
- Re: variable names for different fortrans
- From: PJH
- Re: variable names for different fortrans
- From: Beliavsky
- variable names for different fortrans
- Prev by Date: RE: complex number & sort
- Next by Date: Re: complex number & sort
- Previous by thread: Re: variable names for different fortrans
- Next by thread: Re: variable names for different fortrans
- Index(es):
Relevant Pages
|