| Re: Beginer question about the @ usage [message #44982 is a reply to message #44850] |
Wed, 27 July 2005 14:13   |
![Paul Van Delst[1] is currently offline](theme/default/images/xoffline.png.pagespeed.ic.XRkd1fkXye.png "Paul Van Delst[1] is currently offline")
Paul Van Delst[1]
Messages: 1157
Registered: April 2002
|
Senior Member |
|
|
Mathieu Malaterre wrote:
> BTW Paul,
>
> Did you on purpose use lower case for function and upper case for
> procedure or is this only pure coincidence ? Seems like people prefer
> the FORTRAN approach where everything is in upper case, (except the
> filename which seems to have to be in lower case).
Coming from the unix world where there is filename case sensitivity, the filenames should be all
lowercase. The name of the function or procedure in the file can be whatever you prefer.
My personal preference (that I also use in my Fortran95 code) is that IDL
statements/keywords/procedures/functions/etc are in all upper case. My own routines are usually
combos of upper and lower with underscores tossed in, but never all upper. Examples I type in to
this newsgroup don't necessarily count :o)
My recommendation is to type stuff in such a way as to make the code as readable and understandable
as possible -- to you and others. How you achieve that (via case, indenting, naming conventions,
comments etc) is up to you and subject to your own personal tastes (IMO). As long as you're
consistent and your code is understandable[1], don't listen to anyone that tells you you must do
something a particular way[2]
paulv
[1] If a typical non-IDL knowledgable 12-15 year old can understand your code, you're doing all
right. If no adolescents are available, any colleague will probably do. :o)
[2] Something I suffer from, unfortunately. It drives me nuts when people give me code that isn't
lined up "correctly"! :oD
--
Paul van Delst
CIMSS @ NOAA/NCEP/EMC
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
