Unfortunately, it does not seem to work - after replacing
this DLL, SlickEdit fails to start with a whole bunch of errors
about missing symbols.
On the second thought, it occurred to me: why is that the instructions
are asking me to replace
vsapi.dll but the file is called
cparse-2019-06-08.dll?
With that, I replaced
cparse.dll instead. The file sizes are similar and SlickEdit
seems to be happy to start. It even recognizes types in global/class variables
now. So, yay, thank you! Time to create an official hot fix
While we are on this topic, there are other places where types can be specified
in Python 3. For example, a typical function declaration would look
like that:
def do_something(foo: str, bar: int) -> List[bool]:
pass
The current context tagging logic in SlickEdit seems to understand
this. At least I can navigate between functions without issues.
The only "peculiarity" that I see is that in the Defs tab on the left
functions are shown with the type separated by a space.
So, the above function would look like this:
do_something(foo str, bar int)
I do not know if this is the intended behavior or not. The only
consequence that I can see of this is that autocomplete for
parameters at the function call does not work. More specifically,
if I have a variables called "foo" and "bar", SlickEdit automatically
substitutes them when calling
do_something() - but only if the function
is declared without types. With types, this does not work - SlickEdit
seems to be looking for variables called "foo str" and "bar int"
respectively.