Skip to content
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

ocamldoc and functor arguments #2486

Closed
vicuna opened this issue Apr 21, 2004 · 2 comments
Closed

ocamldoc and functor arguments #2486

vicuna opened this issue Apr 21, 2004 · 2 comments
Labels

Comments

@vicuna
Copy link

vicuna commented Apr 21, 2004

Original bug ID: 2486
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)

Bug description

Full_Name: Virgile Prevosto
Version: 3.07+2
OS: Linux (Debian 3.0)
Submission from: mpiat2314.ag2.mpi-sb.mpg.de (139.19.20.103)

Hi,
ocamldoc seems to have problems with functors whose arguments have type
constraints, as in the example below:

module type A = sig type t val foo: string end
module B =
functor (A1: A with type t = string) ->
struct let foo1 = A1.foo end

The generated documentation for B is (with ocamldoc -html)

module B: functor (A1 : sig end) -> sig end

Parameters:
A1 : sig end

val foo1 : string

It would be better to have "Parameters A1: A" (or even better to keep also the
type constraint).

@vicuna
Copy link
Author

vicuna commented Apr 23, 2004

Comment author: administrator

Hello,

This is alerady fixed in the current CVS: the generated documentation in Latex
and HTML is more consistent with the original code. In your example uou will
have:
module type A = sig .. end

module B:
functor (A1 : A with type t = string) -> sig .. end

with (hopefully correct) links to modules and module types.

Thanks for your report.

Friendly,

Maxence

@vicuna
Copy link
Author

vicuna commented Apr 23, 2004

Comment author: administrator

MGU - fixed

@vicuna vicuna closed this as completed Apr 23, 2004
@vicuna vicuna added the bug label Mar 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant