[#9722] Kernel#system broken inside Dir.chdir(&block) if system command doesn't have shell characters — <noreply@...>

Bugs item #7278, was opened at 2006-12-14 13:59

8 messages 2006/12/14

[#9749] System V IPC in standard library? — Steven Jenkins <steven.jenkins@...>

Back in August, I needed a semaphore to serialize access to an external

14 messages 2006/12/19

[#9753] CVS freeze — SASADA Koichi <ko1@...>

Hi,

20 messages 2006/12/20
[#9755] Re: [ruby-dev:30039] CVS freeze — SASADA Koichi <ko1@...> 2006/12/20

Hi,

[#9757] Re: [ruby-dev:30040] Re: CVS freeze — SASADA Koichi <ko1@...> 2006/12/20

Hi,

Re: rdoc aborting?

From: Hugh Sasse <hgs@...>
Date: 2006-12-08 15:35:01 UTC
List: ruby-core #9684
On Sat, 9 Dec 2006, Hadmut Danisch wrote:

> Hi,
> 
> I just had a strange behavior of rdoc. I tried to run rdoc on a ruby
> code file, but found that only the first class got documented. I
> stripped the example down to
> 
> 
> class Config
> 
>   def update
>     ist <<l

That looks exactly like the beginning of a "here document" that doesn't
end.
>   end
> 
> end
> 
> class Test
> end
> 
> 
> 
> 
> rdoc (debian unstable) generates documention only for the first
> class. But when putting a space between << and l  or removing the

And that is why it works when you have a space. Then it looks like
a shift-left or append.
bash-2.05$ ruby -c

class Config

  def update
    ist <<l
  end

end

class Test
end

-:12: can't find string "l" anywhere before EOF
-:5: parse error, unexpected $, expecting tSTRING_CONTENT or tSTRING_DBEG or tSTRING_DVAR or tSTRING_END
bash-2.05$ 


> line, it works. 
> 
> Any reason why rdoc aborts without error message?
> 
> regards
> Hadmut
> 
        Hugh


In This Thread

Prev Next