-
Notifications
You must be signed in to change notification settings - Fork 41
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
TO_LAB should put all global variables into a global structure #23
Comments
jphickey
added a commit
to jphickey/to_lab
that referenced
this issue
Feb 7, 2020
This creates a TO_LAB_Global namespace to isolate these global variables from other modules and prevent collision.
jphickey
added a commit
to jphickey/to_lab
that referenced
this issue
Feb 11, 2020
jphickey
added a commit
to jphickey/to_lab
that referenced
this issue
Mar 2, 2020
This creates a TO_LAB_Global namespace to isolate these global variables from other modules and prevent collision.
astrogeco
pushed a commit
that referenced
this issue
Mar 9, 2020
This creates a TO_LAB_Global namespace to isolate these global variables from other modules and prevent collision.
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
TO_LAB has several "bare" global variables, which are not namespace-qualified. These should all be put into a global structure, similar to the way other modules isolate their global varables.
Describe the solution you'd like
Implement a
TO_LAB_Global
data structure to isolate these values from the global namespace.Additional context
Note that global variables in shared objects are by default put into a "common" section which can have weird effects on namespace clashes. This is why it is important to put them into a struct (which in this case is basically a namespace isolation mechanism).
Requester Info
Joseph Hickey, Vantage Systems Inc.
The text was updated successfully, but these errors were encountered: