From: Matthias Lampert <ml@...>
Date: 2001-08-08T16:06:24+09:00
Subject: [ruby-talk:19355] Bug in raising RuntimeError?

Hi, folks!

Now that we talking about some assertive programming here, 
there's something that seemingly needs assertion in Ruby itself.
Here's what I found:



###############################################################


$  ruby -e 'nil or raise RuntimeError, "Eh? "'
-e:1: Eh? (RuntimeError)


$ ruby -e 'nil or raise RuntimeError, "Eh? ", caller'
-e:1: [BUG] Segmentation fault
ruby 1.6.3 (2001-03-19) [i686-linux]
Aborted


################################################################



Perhaps Ruby is not happy to proceed `caller' in a one-liner.  But 
in my eyes this can't be a sensible reason for a segmentation fault!
Another internal Ruby exception for this event would be OK, though.

So, this turns out into two questions:

    <> Is this one fixed in 1.6.4?

    <> Would upgrading clobber my <irony>spiffy, nifty, 
       super-duper</irony> library enhancements I have written for 
       my purposes or integrated from third parties -- and placed 
       in the site-ruby directory?

Any experience available?  Ask me if you need more information about
my system.



Live long and prosper!

-- 

Hippo (aka Matthias Lampert)
Just another XP and Ruby fan