[#35446] [Ruby 1.9 - Bug #4477][Open] Kernel:exec and backtick (`) don't work for certain system commands — Joachim Wuttke <j.wuttke@...>

10 messages 2011/03/07

[#35476] [Ruby 1.9 - Bug #4489][Open] [PATCH] Encodings with /-(unix|dos|mac)\Z/ — "James M. Lawrence" <quixoticsycophant@...>

20 messages 2011/03/10

[#35552] [Ruby 1.9 - Feature #4523][Open] Kernel#require to return the path of the loaded file — Alex Young <alex@...>

14 messages 2011/03/24

[#35565] [Ruby 1.9 - Feature #4531][Open] [PATCH 0/7] use poll() instead of select() in certain cases — Eric Wong <normalperson@...>

33 messages 2011/03/28

[#35566] [Ruby 1.9 - Feature #4532][Open] [PATCH] add IO#pread and IO#pwrite methods — Eric Wong <normalperson@...>

12 messages 2011/03/28

[#35586] [Ruby 1.9 - Feature #4538][Open] [PATCH (cleanup)] avoid unnecessary select() calls before doing I/O — Eric Wong <normalperson@...>

9 messages 2011/03/29

[ruby-core:35548] Re: NoMethodError#message may take very long to execute

From: Adiel Mittmann <adiel@...>
Date: 2011-03-23 21:32:48 UTC
List: ruby-core #35548
Hello,

On Thu, Mar 24, 2011 at 04:47:08AM +0900, NARUSE, Yui wrote:
> (2011/03/24 1:34), David Yip wrote:
> > Your report might get more attention in Ruby's issue tracker:
> > http://redmine.ruby-lang.org/
> 
> Yeah, you should post proposals to issue tracker.

I will post it there, thanks.

> > Of course I can write a #to_s for all my objects, but the point is that I didn't
> > call #to_s or #inspect, I called #message on an exception object, which then
> > takes a few minutes just to return a short string.
> 
> You (or the library's author) should write suitable #inspect.
> #inspect is called when you use another methods like Kernel#p or irb.
> 
> So similar problem happens with such objects when you use p or irb.
> Your abstract proposal "to always print out the simpler representation
> given by rb_any_to_s" is not correct way.

But when you use Kernel#p or irb, you expect your object to be printed out. When
you call NoMethodError#message, you don't -- you just want a quick and
informative message.

-- 
Adiel Mittmann

In This Thread

Prev Next