Apparently you didn't, else you wouldn't post the same arguments again.
Well I have had to keep repeating myself because I didn't understand, until looking_for_help pointed it out, what the differences were.
looking_for_help said:
the Wurst plugin for Eclipse however offers semantic information
This is the first time this has been clarified, which would have simplified things a lot.
I haven't compared Nestharus' Eclipse files to Wurst's, so while both have Eclipse support, it appears there is good documentation on what Wurst's offers for features in Eclipse.
Frotty said:
Apparently you didn't, else you wouldn't post the same arguments again.
@Frotty No I read all your posts in the past, and I went back re-read them again. To clarify, I will go through each of your posts concerning Eclipse usage where it was not immediately obvious to me what looking_for_help points out explicitly. Remember I am
not a programmer. It isn't an excuse or shield, but only that I'm ignorant and would benefit from more verbose explanation as after six posts I still did not understand.
Frotty said:
Eclipse autocomplete is far, far superior over TESH or the newer alternative in the editing tools forum.
Right. This autocomplete feature works with any language, including vJASS?
It is context sensitive (which means it suggests fitting stuff and not just everything)
A context sensitive search works independent of the language, since it's just looking at strings, unless it incorporates semantic information in the search (that would be complicated for interface).
uses a fuzzy search (which means entering .get will suggest ".getZ" as well as ".posGet" or even ".together"),
Just a substring search, which should work for any language.
has built-in hot-doc providing documentation about even suggested function,
Not sure if this in Nestharus' files for using Eclipse with vJASS.
works for class constructors,
I believe this is getting to semantic information specific to the language, in which case this is exclusive to Wurst.
automatically places brackets (but only when needed),
Works for any language if the delimiters / scope words are defined.
and the main improvement is that it works with custom code (packages, globals, functions, classes, ...) and not just common.j and blizzard.j
This is also language specific. I see now. When I read this the first time I confused semantic, language specific features with syntax / string search based ones and so assumed that Eclipse automatically gives this to every language without being told explicitly. However, it appears this is not the case, that Eclipse can't infer the semantics of the language.