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: 4366 Reporter: jm Assigned to:@zoggy Status: closed (set by @zoggy on 2007-11-12T08:42:14Z) Resolution: won't fix Priority: normal Severity: major Version: 3.10+dev Category: ocamldoc Monitored by: jm
Bug description
% cat file.ml
module type M =
sig
type t
end
module M =
struct
end
% <calls to ocamlc/ocamldoc>
% ls doc/html/File.*
doc/html/File.html doc/html/File.M.html
File.M.html contains the documentation for [module type] M,
the documentation for [module] M is nowhere,
and links for it point to the documentation of [module type] M.
The text was updated successfully, but these errors were encountered:
Indeed. But having two different ways of naming html files for module and module type makes html linking very hard, for example in function types: the generator has to know whether each type absolute name refer to a type in a module or a module name, if both exists. This complicates the code a lot. By the way, I'm not convinced that having a module type and a module with the same name is a good choice, since they refer to two different things.
So I keep the current implementation.
Original bug ID: 4366
Reporter: jm
Assigned to: @zoggy
Status: closed (set by @zoggy on 2007-11-12T08:42:14Z)
Resolution: won't fix
Priority: normal
Severity: major
Version: 3.10+dev
Category: ocamldoc
Monitored by: jm
Bug description
% cat file.ml
module type M =
sig
type t
end
module M =
struct
end
% <calls to ocamlc/ocamldoc>
% ls doc/html/File.*
doc/html/File.html doc/html/File.M.html
File.M.html contains the documentation for [module type] M,
the documentation for [module] M is nowhere,
and links for it point to the documentation of [module type] M.
The text was updated successfully, but these errors were encountered: