You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the mailing list, it seems there may be no way to instruct ocamlbuild that certain suffixes should be treated like interfaces or implementations, and in the event that they are treated as such, how to resolve the respective interfaces:
Specifically, here is how all of the ocamlc/ocamldep/* suite of commands should be effected by the file extension:
This can currently be accomplished by moving .xyz/xyzi files to .ml/.mli files respectively in a myocamlbuild rule, however this results in incorrect error messages.
Gabriel suggested a lexer preprocessor rule to fool ocaml's compiler into reporting errrors in terms of the original source file, even if renamed to a .ml.
Original bug ID: 6949
Reporter: jordojw
Status: resolved (set by @damiendoligez on 2017-03-01T10:44:46Z)
Resolution: open
Priority: normal
Severity: feature
Category: -for ocamlbuild use https://github.com/ocaml/ocamlbuild/issues
Monitored by: @hcarty
Bug description
According to the mailing list, it seems there may be no way to instruct ocamlbuild that certain suffixes should be treated like interfaces or implementations, and in the event that they are treated as such, how to resolve the respective interfaces:
Specifically, here is how all of the ocamlc/ocamldep/* suite of commands should be effected by the file extension:
/.xyz
ocamlc/ocamldep -pp convertXyzProgram -impl theFile.xyz -intf-suffix xyzi
/.xyzi
ocamlc/ocamldep -pp convertXyzProgram -intf theFile.xyzi
Gabriel Scherer suggested that I file an issue here, and that it wouldn't be too difficult to implement this in ocamlbuild.
The text was updated successfully, but these errors were encountered: