There is still a problem with ocamldoc content
It turns out that the output of the lexer is not enough, and may be ambiguous in some cases:
COMMENT, COMMENTCONT may mean a 'wrong' ocamldoc tag which caused the token to be split (eg '(* {v *)')
but it may also be caused by a legit COMMENTCONT meaning the end of an ocamldoc code block:
'(* {[ (* *) ]} *)' yields COMMENT, ODOC_CODE, COMMENT, COMMENTCONT
Fixed problems with crazy ocamldoc comments mixups
fix: tiny bug with multiple comments at end of block
Fixed bug of library function is_at_top for 2-keyword constructs
(module type, let module)