Skip to content
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

designate loaded version of a module without knowing it #366

Closed
xdelaruelle opened this issue Nov 8, 2020 · 0 comments
Closed

designate loaded version of a module without knowing it #366

xdelaruelle opened this issue Nov 8, 2020 · 0 comments
Milestone

Comments

@xdelaruelle
Copy link
Member

It is sometimes desired to perform an action over the loaded version of a module (for instance to display its content). Using the bare module name, for instance foo when foo/1.0 is loaded, will not work as this name designates the default version of the module, which for instance is foo/2.0 not our loaded version foo/1.0.

Adding a new symbolic version to the advanced version specifiers named loaded, would do the trick: module display foo@loaded will automatically resolve to the version of foo which is currently loaded.

@xdelaruelle xdelaruelle added this to the 4.7 milestone Nov 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant