-
-
Notifications
You must be signed in to change notification settings - Fork 189
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
Add TLA_PATH environment variable to load modules from #490
Comments
Does @informalsystems have the resources to provide a pull request? |
In principle, yes, but I am not sure about the whereabouts of the file reading operations in the SANY parser. |
Since |
Thanks! I will have a look. |
@konnov Are you still pushing this? |
Not really. I was stuck at how Eclipse handles filenames. So I guess the related PR #493 needs some expertise in Eclipse. |
@lemmy what do you think about also adding this as a TLC command line option? You can define additional directories to search for TLA files when running TLC. This would also help when outputting TE specs to a subdirectory; you can switch working directory to that subdirectory, then run TLC on the TE spec while asking TLC to look for the original spec in the parent directory via a command line option. This is also nice because running TLC on a spec identified by absolute path (rather than in current working directory) does not seem to be currently supported. |
It would be great to have a standard environment variable, e.g., called
TLA_PATH
. Similar toPATH
,PYTHON_PATH
,JAVA_LIBRARY_PATH
, etc., it would list directories, from which the TLA+ tools would pull the library modules.The text was updated successfully, but these errors were encountered: