Type Specifier confuses editor?
Posted: Wed May 22, 2019 2:10 am
Hi Cherry Folks...
FYI, I was experimenting with Generic Types the other day and noticed that including a type specification in "<type>" form in a class definition confuses the "module explorer" part of the editor in VMD.
This example shows what I mean (and isn't intended to compile/run):
You can see there's no entry for class Foo, but its two member functions are displayed.
Getting rid of the whole "Implements" part puts things right:
Now we can see Foo again.
But it isn't "Implements" that's causing the confusion, it's "<Integer>":
Really, it seems to be the fact that there are "<>" characters that's the root of the confusion.
It's not a big deal as the confusion doesn't affect the compile-ability of the code, but it isn't quite expected behaviour either.
Or am I the confused one?
Cheers,
--
Terry McG
FYI, I was experimenting with Generic Types the other day and noticed that including a type specification in "<type>" form in a class definition confuses the "module explorer" part of the editor in VMD.
This example shows what I mean (and isn't intended to compile/run):
You can see there's no entry for class Foo, but its two member functions are displayed.
Getting rid of the whole "Implements" part puts things right:
Now we can see Foo again.
But it isn't "Implements" that's causing the confusion, it's "<Integer>":
Really, it seems to be the fact that there are "<>" characters that's the root of the confusion.
It's not a big deal as the confusion doesn't affect the compile-ability of the code, but it isn't quite expected behaviour either.
Or am I the confused one?
Cheers,
--
Terry McG