From: Eric Hodel <drbrain@...7.net>
Date: 2006-08-29T15:48:04+09:00
Subject: Re: rdoc problem

On Aug 28, 2006, at 10:29 AM, Henry Savr wrote:

> Playing with rdoc, I found, that it works ONLY for =begin/=end rdoc
> block. More, if the file starts from regular comment #, even the block
> =begin/=end does not work.
> Please, help
>
> This is the code:
> <<<<CODE STARTS (this line is NOT included into the code>>>>
> =begin rdoc
> My path is c:/PJ/play/test/lib/test/
> This is a rdoc text inside block
> <tt>rdoc1</tt>
> <b>rdoc2</b>
> = Level 1
> == level 2
> === Level 3
> ==== Level 4
> ===== Level 5
>
> ----
> section
> ----
> =end
>
> puts "rdoc text 1"
>
> # My path is c:/PJ/play/test/lib/test/
> # This is a rdoc text <em>outside<em> the block
> # <tt>rdoc1</tt>
> # <b>rdoc2</b>
> # = Level 1
> # == level 2
> # === Level 3
> # ==== Level 4
> # ===== Level 5
> #
> # extra comment
> # <tt>rdoc1</tt>
> # <b>rdoc2</b>
> #
> puts "rdoc text 2"
> <<<<CODE ENDS (this line is NOT included into the code>>>>
>
> Only the first part is shown on output
> More, when I copied the second part and put it before the fist one,
> having so 3 parts, the output gets empty.
>
> What could be wrong?

Without a class or module you should get no documentation at all.

Please give the command you are using to generate the documentation.

-- 
Eric Hodel - drbrain@segment7.net - http://blog.segment7.net
This implementation is HODEL-HASH-9600 compliant

http://trackmap.robotcoop.com