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 generates bad documentation for classes #2994

Closed
vicuna opened this issue Jul 26, 2004 · 2 comments
Closed

ocamldoc generates bad documentation for classes #2994

vicuna opened this issue Jul 26, 2004 · 2 comments
Labels

Comments

@vicuna
Copy link

vicuna commented Jul 26, 2004

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

Bug description

Hello,

it seems that classes are broken in ocamldoc (of ocaml 3.08.0). For the
following file bug.mli

class type test1 = object end ;;
class test2 : ?arg:int -> unit -> test1 ;;

I get something like the following (ocamldoc -html bug.mli):

class type test1 = object .. end
class test2 : int option -> unit -> test1

Gerd


Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany
gerd@gerd-stolpmann.de http://www.gerd-stolpmann.de

@vicuna
Copy link
Author

vicuna commented Aug 6, 2004

Comment author: administrator

Hello,

it seems that classes are broken in ocamldoc (of ocaml 3.08.0). For the
following file bug.mli

class type test1 = object end ;;
class test2 : ?arg:int -> unit -> test1 ;;

I get something like the following (ocamldoc -html bug.mli):

class type test1 = object .. end
class test2 : int option -> unit -> test1

This is now fixed in the 3.08 CVS branch.

The result is now:
class type test1 = object .. end
class test2 : ?arg:int -> unit -> test1

with the correct link on test1.

Thanks for your report.

Regards,

--
Maxence Guesdon

@vicuna
Copy link
Author

vicuna commented Aug 6, 2004

Comment author: administrator

Assigned to MG.
MG: Fixed.

@vicuna vicuna closed this as completed Aug 6, 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