-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle VBScript's case insensitivity #163
Labels
scripting
Related to the VBScript port
Comments
One cheap workaround could be on the vpm-controller side, like |
@neophob is this a blocker for you? |
no - i will add the workaround and reference this issue. See https://github.com/vpdb/vpx-js/commits/feature/wpc-integrationtest |
neophob
added a commit
that referenced
this issue
Nov 18, 2019
update emu readme work around issue #163
neophob
added a commit
that referenced
this issue
Nov 18, 2019
update emu readme work around issue #163
freezy
pushed a commit
that referenced
this issue
Nov 18, 2019
update emu readme work around issue #163
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Still a few items on the list:
ScopeHandler
proxy)VbsApi
)VbsApi
)VbsApi
)And probably more.
TODO
COM Implementations
I don't think they can be handled at compile time, since they are instances created by the table script we cannot query when compiling (table elements, enums etc work because we have them all at compile time).
So the
getObject()
method should return aScopeHandler
-like proxy that keeps an index when accessing props and methods and returns the correctly spelled version.Local Scope
This should be doable at compile time, since all variables are declared in the same scope and don't come from other included files we know nothing about. I think I've tried this already but
ascope
choked at the AST we have when we do this.The text was updated successfully, but these errors were encountered: