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

Improving the --version directive #7748

Closed
vicuna opened this issue Feb 28, 2018 · 7 comments
Closed

Improving the --version directive #7748

vicuna opened this issue Feb 28, 2018 · 7 comments

Comments

@vicuna
Copy link

vicuna commented Feb 28, 2018

Original bug ID: 7748
Reporter: igo_weiqi_baduk
Assigned to: @dra27
Status: acknowledged (set by @dra27 on 2018-02-28T18:18:38Z)
Resolution: open
Priority: low
Severity: tweak
OS: Linux x86_64
Version: 4.06.1
Category: compiler driver
Monitored by: @gasche

Bug description

Displaying the full name (with the variant +afl, +flambda...) of the active compiler would be great.

Great also to have the toplevel displaying this full version name (on its first line).

@vicuna
Copy link
Author

vicuna commented Feb 28, 2018

Comment author: @dra27

Note #465 is aimed at solving this (this GPR was approved - subject to changes discussed in it) at a developer meeting last November, but I haven't had time to rebase it yet).

I'm not sure that we can alter the format of the version returned, because there are probing scripts which depend on its format.

Note that can you already determine a lot of this from the output of ocamlc -config.

@xavierleroy
Copy link
Contributor

Re-classifying as a feature wish. @dra27: is #465 stalled completely, or do you plan to resurrect it?

@dra27
Copy link
Member

dra27 commented Mar 27, 2019

@xavierleroy - on opam stuff for the next few months, and hoping finally to revisit #465, yes!

@github-actions
Copy link

github-actions bot commented May 7, 2020

This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.

@github-actions github-actions bot added the Stale label May 7, 2020
@dra27 dra27 removed the Stale label May 7, 2020
@github-actions
Copy link

This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.

@github-actions github-actions bot added the Stale label May 12, 2021
@gasche
Copy link
Member

gasche commented May 12, 2021

This feature request would require a substantial amount of work (depending on how it is designed), and it appears that no one is interested in working on it for now. Closing; let us know if there is interest in working on it, we can always reopen.

@gasche gasche closed this as completed May 12, 2021
@dra27
Copy link
Member

dra27 commented May 12, 2021

I agree - I think your new --config-var (#1430) in 4.08 dealt with the scripting side of this. The recent change in opam-repository to use the ocaml-option- packages also makes this "probing" of features slightly less unclear.

For the toplevel, it might be tempting to having a #config - but the main variants are mostly uninteresting in the toplevel (flambda and afl aren't relevant and no-naked-pointers, no-flat-float-array affect C the runtime, so it's not clear what displaying that in every toplevel adds)

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

4 participants