| Re: Ambiguous keyword abbreviation error [message #55823 is a reply to message #55819] |
Tue, 11 September 2007 12:23  |
Foldy Lajos
Messages: 268
Registered: October 2001
|
Senior Member |
|
|
On Tue, 11 Sep 2007, Jonathan Greenberg wrote:
> So I have NEVER seen this error before, and now I've seen it twice in one
> day, with two completely different programs (one I wrote, one I didn't):
>
> Ambiguous keyword abbreviation: [name of function/program]
>
> I've been poring through the user group here and I *sort-of* see what is
> going on, but what ARE the rules for naming keywords? I was under the
> mistaken notion that these were like named variables, so as long as I had
> unique names for each one I was good to go. Does this behavior differ from
> system to system (the 2nd of the two failures was from a program that I have
> to assume has been run at least ONCE before I got a hold of it, so it should
> have shown the error before I received it -- this may be an incorrect
> assumption...)? Is there an easy way to disable this, or do I have to go
> back through and rename keywords all over the place...
>
> Thoughts? Thanks!
>
> --j
>
Keywords must be unique and they can not be abbreviations of other
keywords. Have you ever wondered why IDL uses LONG for 32 bit integers and
L64 (instead of LONG64) for 64 bit ones?
regards,
lajos
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
