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
Original bug ID: 1125 Reporter: administrator Status: closed Resolution: fixed Priority: normal Severity: feature Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Chris Quinn
Version: 3.04
OS:
Submission from: 212.42.169.63 (212.42.169.63)
A useful thing it is to be able to put type
declarations alone into an interface file, so
saving on an unnecessary implementation file
and keeping them synchronised.
One can then "open" this interface.
But the same cannot be done for "include"
because the linker complains about an undefined
Global.
This seems a reasonable thing to expect when there
are no value definitions.
I would find it useful because I auto-generate
interfaces but want to re-home them in manually
written code.
Any chance?
The text was updated successfully, but these errors were encountered:
A useful thing it is to be able to put type
declarations alone into an interface file, so
saving on an unnecessary implementation file
and keeping them synchronised.
One can then "open" this interface.
But the same cannot be done for "include"
because the linker complains about an undefined
Global.
This seems a reasonable thing to expect when there
are no value definitions.
Agreed. This is something I overlooked when writing the compilation
scheme for "include". I'll fix this for the next release.
Original bug ID: 1125
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: feature
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Chris Quinn
Version: 3.04
OS:
Submission from: 212.42.169.63 (212.42.169.63)
A useful thing it is to be able to put type
declarations alone into an interface file, so
saving on an unnecessary implementation file
and keeping them synchronised.
One can then "open" this interface.
But the same cannot be done for "include"
because the linker complains about an undefined
Global.
This seems a reasonable thing to expect when there
are no value definitions.
I would find it useful because I auto-generate
interfaces but want to re-home them in manually
written code.
Any chance?
The text was updated successfully, but these errors were encountered: