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
Description de -pack dans le manuel #4148
Comments
Comment author: @alainfrisch I propose to postpone this, to avoid delaying the release. |
Comment author: @damiendoligez About point (2), this is exactly the same as when producing a .cmo file, right? |
Comment author: @alainfrisch
Yes, indeed. But the manual says, about -pack: << Build a bytecode object file (.cmo file) and its associated compiled interface (.cmi) that combines .. >> and from this, it is hard to know that one can provide an explicit .mli. |
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. |
Original bug ID: 4148
Reporter: @alainfrisch
Status: acknowledged (set by @damiendoligez on 2006-11-15T12:16:33Z)
Resolution: open
Priority: normal
Severity: minor
Category: documentation
Related to: #7223
Monitored by: @Chris00
Bug description
La description de -pack dans le manuel devrait indiquer les faits suivants:
il est possible de fournir des .cmi (qui n'exportent pas de valeurs) à packer;
si un .mli est présent pour le module packé, alors il doit y avoir un .cmi
correspondant qui est compatible avec le type du module produit; le .cmi
est produit par -pack seulement si le .mli n'existe pas.
The text was updated successfully, but these errors were encountered: