| Re: Name Space Conflicts [message #47859] |
Wed, 08 March 2006 13:17  |
![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 |
|
|
David Fanning wrote:
> Paul Van Delst writes:
>
>
>> Why not prefix it with FSC_ like some of your other code?
>
>
> Primarily because once you stick a prefix on a program,
> the code has a way of living (and embarrassing you!)
> forever. :-(
Well, if that's what you're worried about, the name of the file won't prevent it.
> And most of my program names are already too long to
> type comfortably, and I've had a typing class. I don't
> think there is a good solution. But I do think RSI ought
> to come up with something beside the order in !PATH
> for sorting this stuff out. In the IDLDE it is easy
> to rearrange your path to suit you, but this is pretty
> much a nightmare in the UNIX world, as far as I can
> tell. At least no one taking an IDL programming class
> from me and working with a UNIX machine has the foggiest
> idea how to do it.
If it's a toss up between a name too long to type comfortably and not working (now or in
the future) due to name space clashes, I'll take the former. And given my verbosity when
it comes to names (see below), "FSC_IMGSCL" is nothing! :o)
paulv
p.s. Good lord, did I write this? :
FUNCTION read_ascii_transmittance_coefficients, sensor_id, $
input_n_channels, $
predictor_index, $
transmittance_coefficients, $
file_path = file_path, $
sort_predictors = sort_predictors, $
smooth_coefficients = smooth_coefficients
And it's still relatively generic. I'd need to prefix it with "pvd_" or somesuch to be
super, ultra sure.....
--
Paul van Delst
CIMSS @ NOAA/NCEP/EMC
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
