How to get a different color for a non existing variable ?

[PGilbert]

While typing the name of a global variable that does not exist (because it is misspelled or nonexisting) in a function, is it possible to change the color of that variable name to another color so we know that it is misspelled or nonexisting?

I see in the color scheme that there is the color for a global variable but what about a global variable that does not exist? Exist or does not exist seems to be the same color.

Thanks in advance.

[Phil Last]

Only a guess but it seems most likely that the designer has chosen to lump everything not locally defined or a global function, operator or script together and decided to call them "global variable" rather than "undefined". A matter of taste. If a new type were defined without extending the list being consulted by autocomplete it would probably fall into the same catchall.

[PGilbert]

Thanks Phil for your thoughts. Coming from APL2000 I miss that feature that we had, it is useful when you look at an already written function and the global variable name does not exist anymore, you can catch it right away. The programmer is more productive with such a feature.

Hopefully, we will have it one day with Dyalog also.

[Vince|Dyalog]

Hi Pierre,

I have logged your request as RFE 19207.

Regards,

Vince

[PGilbert]

Many thanks Vince.

[ArrayMacNB]

This color would save the need to glance down at the 'CurObj:' line at the bottom, yes. Given it does not seem to be a big effort to glance down, I am not sure that the savings justify an interpreter change. YMMV (or VMPV?), of course.

[kai]

This is about spotting anything undefined with a single glance no matter how many variables there are. CurObj does not help then.

I am strongly in favour of this feature request.