| Re: IDL limits [message #12461 is a reply to message #4790] |
Mon, 03 August 1998 00:00   |
davidf
Messages: 2866
Registered: September 1996
|
Senior Member |
|
|
Dick French writes in response to Bob Mallozzi:
> Robert - One limit that I have run up against and can't find
> documentation for relates to KEYWORD names. I tried to define
> keywords XMIN_ABSOLUTE and XMIN_RELATIVE, say, and got
> an error message about ambiguous keyword definitions. Can someone point
> me to the documentation on unique keyword recognition? I have gotten
> around this by using different names, but it would be nice to
> know the rules of the game!
Dick, your description of the problem seems highly unlikely.
If you had defined a procedure with these two keywords, like
this:
PRO JUNK, XMIN_Absolute=absolute, XMIN_Relative=relative
there would be absolutely (pun intended) no problem. Where
you MIGHT run into a problem is if you called the procedure
like this:
JUNK, XMIN=5
In this case, you WOULD get an error message about ambiguous
keyword definitions because IDL would not have enough letters
to distinguish between the two keywords in the "keyword table"
that gets created when the procedure is compiled. You must
use enough keyword letters in the keyword name to identify that
keyword unambiguously.
For example, if you had named the keywords Absolute_XMin and
Relative_XMin, you could call the procedure like this:
JUNK, A=5
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting
E-Mail: davidf@dfanning.com
Phone: 970-221-0438
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
