[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#245401: marked as done (ocamldoc: empty lines not permitted within {[ .. ]})

Your message dated Sun, 07 Jan 2007 01:53:47 +0100
with message-id <45A0449B.6060806@ens-lyon.org>
and subject line Bug#245401: ocamldoc: empty lines not permitted within {[ .. ]}
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: ocaml
Version: 3.07.2a-2
Severity: normal

The documentation doesn't mention it, but the {[ ... ]} construct in
ocamldoc-parsed comments in .mli files may not contain empty lines
(though any number of lines is otherwise permissible.)

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.4
Locale: LANG=C, LC_CTYPE=C

Versions of packages ocaml depends on:
ii  libc6                       2.3.2.ds1-11 GNU C Library: Shared libraries an
ii  libncurses5-dev             5.4-3        Developer's libraries and docs for
ii  ocaml-base [ocaml-base-3.07 3.07.2a-2    Runtime system for ocaml bytecode 

-- no debconf information

--- End Message ---
--- Begin Message --- 
Package: ocaml
Version: 3.08.0-1

Georg Neis wrote:
> Hello!
> 
> * John Goerzen <jgoerzen@complete.org> wrote:
>> Package: ocaml
>> Version: 3.07.2a-2
>> Severity: normal
>>
>> The documentation doesn't mention it, but the {[ ... ]} construct in
>> ocamldoc-parsed comments in .mli files may not contain empty lines
>> (though any number of lines is otherwise permissible.)
> 
> I think this has been fixed in the meantime.

Thanks for noticing this! I'm closing the bug.

Cheers,

Samuel.

--- End Message ---
Reply to: