|Anonymous | Login | Signup for a new account||2017-02-19 22:24 CET|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005641||OCaml||OCaml internal build/install (Makefiles, configure)||public||2012-06-08 18:45||2012-06-22 07:44|
|Target Version||Fixed in Version|
|Summary||0005641: .mli of compiler files should be installed too|
|Description||It would be useful and convenient to install the .mli of the modules being installed in compiler-libs.|
|Tags||No tags attached.|
|it's not necessary. since you can use ocamlbuild to dump the .inferred.mli|
IMO, the goal of installing compiler-libs is to allow end-users to compile third-party packages that depend on those compiler modules (for instance, some code base analysis tools). Developers of such tools could use .mli files as documentation (technically, they don't need them to compile their work), but one could argue that the .mli files of the compiler don't contain a lot of information, and that developers would actually like to have access to the implementation as well. And I think this is fine: developers of low-level tools, strongly tied to the compiler, will download the source code as a reference.
But if the demand is strong enough, I'm not opposed to installing .mli files.
I agree with Alain Frisch's comment. The .mli of the compiler are not (by a long shot) written in a way that would document the compiler internals. I don't see added value in installing them.
For curiosity, is there any public docs(whether in French or English) about the compiler internals?
|2012-06-08 18:45||guesdon||New Issue|
|2012-06-09 03:29||hongboz||Note Added: 0007530|
|2012-06-13 19:54||frisch||Note Added: 0007554|
|2012-06-17 10:25||xleroy||Note Added: 0007563|
|2012-06-17 10:25||xleroy||Status||new => resolved|
|2012-06-17 10:25||xleroy||Resolution||open => suspended|
|2012-06-18 14:47||hongboz||Note Added: 0007565|
|Copyright © 2000 - 2011 MantisBT Group|