Better descriptions (and export parameters) around the dependency generator for OCaml #7576
Comments
|
Comment author: @dra27 Please stop spamming this bug-tracker with incomplete or non-reports! As a rule of thumb, if you are categorising something as severity "feature", but your report includes question marks, then it should not be here. If, having found the answers to your two questions above somewhere else, you find you would still like the example in the manual to be "improved", you may either come back to Mantis with a concrete suggestion or submit a pull request for it (the particular file is https://github.com/ocaml/ocaml/blob/trunk/manual/manual/cmds/depend.etex). |
|
Comment author: @elfring I proposed to make another information source a bit better. I try to check also the general change acceptance before I offer a special pull request for a registered issue. |
|
Comment author: @elfring How can be achieved that only directories will be exported from the passed filenames in the order in which the specified software components depend on each other? |
|
Comment author: @dra27 You haven't yet demonstrated an improvement to the documentation, and you ask questions the answers for which you should determine elsewhere before logging feature requests here. |
|
Comment author: @elfring It seems that we prefer different communication styles for this issue. I request a data export of directories which are referenced by the specified OCaml source files. |
|
Comment author: @xavierleroy Enough with the reopening games. |
|
Will other contributors dare to continue the clarification of affected software components? |
|
They appear to have continued to since 2017, yes. |
Original bug ID: 7576
Reporter: @elfring
Status: closed (set by @xavierleroy on 2017-07-21T15:29:17Z)
Resolution: not a bug
Priority: normal
Severity: feature
Version: 4.03.0
Category: tools (ocaml{lex,yacc,dep,debug,...})
Related to: #7558
Bug description
The documentation contains the following information:
“…
The typical usage is:
…”
I find that there are more details worth for further software development considerations around such an example.
It will be sufficient to refer to a single source file directory in some use cases.
But I imagine that this interface should also work to some degree when file names are passed as a mixture from several directories.
How good can OCaml module references be mapped to paths in the file system then?
Will it be safer to store the generated dependency file (or the provided data generally) at an other place (than within the same folder)?
Additional information
https://caml.inria.fr/pub/docs/manual-ocaml/depend.html
Support selection of source file names also for other export formats than make rules
#7558
The text was updated successfully, but these errors were encountered: