hsbt_away changed the topic of #ruby-core to: check the latest release candidate for 1.9.1 release ftp.ruby-lang.org:/home/yugui/ruby-1.9.1-r26021+1.tar.bz2
kosaki2 has quit [Ping timeout: 256 seconds]
peta_ has quit [Quit: peta_]
<znz_jp> biff: [ruby-changes:28538] kazu:r40590 (trunk): fix a typo - http://mla.n-z.jp/?ruby-changes=28538
<znz_jp> biff: [ruby-changes:28539] svn:r40591 (trunk): * 2013-05-06 - http://mla.n-z.jp/?ruby-changes=28539
Domon has joined #ruby-core
idkazuma has quit [Remote host closed the connection]
marcandre has joined #ruby-core
cout_ is now known as cout
cout is now known as cout_
cout_ is now known as cout
cout is now known as cout_
cout_ is now known as cout
kosaki2 has joined #ruby-core
Domon has quit [Read error: Connection reset by peer]
Domon has joined #ruby-core
idkazuma has joined #ruby-core
Domon has quit [Ping timeout: 264 seconds]
Domon has joined #ruby-core
Domon has quit [Remote host closed the connection]
tylersmith has quit [Remote host closed the connection]
Domon has joined #ruby-core
tylersmith has joined #ruby-core
idkazuma has quit [Remote host closed the connection]
tylersmith has quit [Read error: Operation timed out]
idkazuma has joined #ruby-core
marcandre has quit [Remote host closed the connection]
r0bgleeson has quit [Ping timeout: 272 seconds]
r0bgleeson has joined #ruby-core
<znz_jp> biff: [ruby-changes:28540] eregon:r40592 (trunk): * compar.c (Comparable#==): fix typo. - http://mla.n-z.jp/?ruby-changes=28540
vondruch has joined #ruby-core
judofyr has joined #ruby-core
shiba___ has quit [Ping timeout: 268 seconds]
kosaki2 has quit [Remote host closed the connection]
Domon_ has joined #ruby-core
Domon has quit [Ping timeout: 268 seconds]
r0bgleeson has quit [Ping timeout: 255 seconds]
idkazuma has quit [Remote host closed the connection]
peta_ has joined #ruby-core
charliesome has joined #ruby-core
shiba___ has joined #ruby-core
Domon_ has quit [Remote host closed the connection]
xibbar has joined #ruby-core
marcandre has joined #ruby-core
peta__ has joined #ruby-core
peta_ has quit [Read error: Connection reset by peer]
<znz_jp> biff: [ruby-changes:28541] akr:r40593 (trunk): * ext/socket/socket.c (socket_s_ip_address_list): Fill sin6_scope_id - http://mla.n-z.jp/?ruby-changes=28541
nagachika has joined #ruby-core
marcandre has quit [Remote host closed the connection]
marcandre has joined #ruby-core
r0bgleeson has joined #ruby-core
kosaki2 has joined #ruby-core
knu has quit [Remote host closed the connection]
xibbar has quit [Remote host closed the connection]
knu has joined #ruby-core
kosaki2 has quit [Remote host closed the connection]
ZachBeta has joined #ruby-core
kosaki2 has joined #ruby-core
kosaki2 has quit [Remote host closed the connection]
charliesome has quit [Quit: Textual IRC Client: www.textualapp.com]
kosaki2 has joined #ruby-core
nagachika has quit [Remote host closed the connection]
vondruch has quit [Remote host closed the connection]
vondruch has joined #ruby-core
judofyr has quit [Remote host closed the connection]
tylersmith has joined #ruby-core
kosaki2 has quit [Remote host closed the connection]
tylersmith has quit [Remote host closed the connection]
headius has joined #ruby-core
vondruch has quit [Quit: Ex-Chat]
tmahoney has joined #ruby-core
tmahoney has quit [Ping timeout: 245 seconds]
tylersmith has joined #ruby-core
ZachBeta has quit [Ping timeout: 252 seconds]
ZachBeta has joined #ruby-core
tenderlove has quit [Remote host closed the connection]
tmahoney has joined #ruby-core
<tmahoney> How can I associate a non-Ruby pthread with a Ruby Thread?
heroux_ has quit [Ping timeout: 245 seconds]
heroux has joined #ruby-core
shiba___ has quit [Ping timeout: 256 seconds]
headius has quit [Quit: headius]
tenderlove has joined #ruby-core
buddhamagnet has joined #ruby-core
buddhamagnet has quit [Quit: leaving]
tmahoney has quit [Ping timeout: 245 seconds]
tmahoney_ has joined #ruby-core
<tmahoney_> If I rb_raise within an rb_rescue, then the program crashes. Can I have the rb_rescue catch my manual rb_raises?
<drbrain> tmahoney_: that shouldn't crash
<tmahoney_> Hmm. Let me make sure that's it.
<drbrain> I say this because you can begin; raise 'one'; rescue; raise 'two'; end
peta__ has quit [Ping timeout: 268 seconds]
<tmahoney_> It turns out I'm using rb_exc_raise, but I don't think that makes a difference.
<tmahoney_> Yeah, even if I use rb_raise, it'll crash. Let me see if a simple example does the same thing.
ZachBeta has quit [Quit: Computer has gone to sleep.]
<drbrain> I think rb_exc_raise is a wrapper around rb_raise
<drbrain> or vice versa
<tmahoney_> Yeah, rb_raise calls rb_exc_raise.
tmahoney_ has quit [Read error: Connection reset by peer]
tmahoney has joined #ruby-core
<tmahoney> Yeah, this crashes
<tmahoney> In Ruby 2.0
<drbrain> I don't think that will work
<drbrain> a) ruby hasn't been set up
<tmahoney> Yeah actually that's not a complete example.
<tmahoney> But assuming it's been set up.
<tmahoney> rb_protect doesn't crash, but rb_rescue does.
<drbrain> b) I think you need to send a valid receiver
<drbrain> well, I suppose Qnil would still work
<drbrain> why does rescue() accept two arguments?
<tmahoney> It takes the first argument as data and the second argument as the exception.
<tmahoney> Data being whatever you pass to rb_rescue
<tmahoney> The last argument to rb_rescue.
<drbrain> I haven't used rb_rescue recently
<tmahoney> Maybe rb_rescue is meant to crash on manual rb_raises.
<drbrain> tmahoney: looking in numeric.c, coerce_rescue raises a TypeError
<drbrain> which is called from do_coerce
<tmahoney> Ah. Maybe it's the type of exception I'm raising.
<tmahoney> If I throw a TypeError instead of my current one, it gets caught correctly.
<tmahoney> Not if I throw a NotImpError.
<drbrain> huh
tmahoney_ has joined #ruby-core
<tmahoney_> My internet connection is having fun today.
<tmahoney_> Ah!
<tmahoney_> rb_rescue only catches subclasses of StandardError. If I use rb_rescue2, I can tell it to catch anything from Exception instead.
<drbrain> oh, yes
<drbrain> I didn't think to ask that
<drbrain> I'm sorry
<drbrain> … by "crashes" did you mean SEGV or "didn't rescue my exception"?
<drbrain> I thought SEGV
<tmahoney_> SEGV.
<drbrain> huh
<tmahoney_> Errr.
<tmahoney_> Well both.
tmahoney has quit [Ping timeout: 272 seconds]
<drbrain> :D
<tmahoney_> Hey look, I left!
<tmahoney_> Yeah, I got EXC_BAD_ACCESS, which means that my exception didn't get rescued (since the application is no longer alive)
<tmahoney_> Cool, if I use rb_rescue2(..., rb_eException) instead of rb_rescue(...), then it's all good.
<tmahoney_> Thanks, drbrain. You've been really helpful lately.
<drbrain> ok, so you were probably reaching the ruby top-level and blowing up
<tmahoney_> Haha blowing up sounds about right.
<drbrain> an rb_rescue2 with rb_eException at top-level will help
idkazuma has joined #ruby-core
hsbt has quit [Ping timeout: 260 seconds]
hsbt has joined #ruby-core
nari_ has joined #ruby-core
nari_ has quit [Ping timeout: 248 seconds]
tenderlo_ has joined #ruby-core
tenderlove has quit [Ping timeout: 246 seconds]