xibbar has quit [Remote host closed the connection]
lopex has quit [Ping timeout: 248 seconds]
<znz_v>
biff: [ruby-changes:27431] akr:r39483 (trunk): * ext/socket/extconf.rb: don't test ss_family and ss_len member of - http://mla.n-z.jp/?ruby-changes=27431
xibbar has joined #ruby-core
<znz_v>
biff: [ruby-changes:27432] zzak:r39484 (trunk): * thread.c: Document Thread::new, clean up ::fork and mention calling - http://mla.n-z.jp/?ruby-changes=27432
<marcandre>
_ko1: Curious as to why #7942 is a feature request. Should be bug, no?
<zzak>
marcandre: grammar question
<marcandre>
Moved to bug, with clearer explanation
<zzak>
"subclasses method"
<marcandre>
zzak: ?
<zzak>
subclass owns the method
<zzak>
is it "subclass' method" then ?
<marcandre>
lol!
<zzak>
im tired
<marcandre>
You're asking me, that's cute.
<marcandre>
Yeah, I think that's correct.
<zzak>
i found better way of writing it
<marcandre>
you're welcome anyways ;-)
<zzak>
When subclassing the Thread class, the +initialize+ method of your subclass will be ignored by ::start and ::fork. Otherwise, be sure to call super in your +initialize+ method.
<znz_v>
biff: [ruby-changes:27442] nobu:r39494 (trunk): test_string.rb: defer ENUMERATORS_WANTARRAY to next major - http://mla.n-z.jp/?ruby-changes=27442
vondruch has joined #ruby-core
schaerli has joined #ruby-core
xibbar has quit [Remote host closed the connection]
shirokuro11 has joined #ruby-core
charliesome_ has joined #ruby-core
charliesome has quit [Disconnected by services]
charliesome_ is now known as charliesome
Domon has joined #ruby-core
takeru_ has joined #ruby-core
nari has quit [Ping timeout: 245 seconds]
takeru_ has quit [Remote host closed the connection]
Domon has quit [Remote host closed the connection]
nari has joined #ruby-core
judofyr has joined #ruby-core
takeru has joined #ruby-core
takeru has quit [Remote host closed the connection]
<znz_v>
biff: [ruby-changes:27443] naruse:r39495 (trunk): * string.c (str_byte_substr): don't set coderange if it's not known. - http://mla.n-z.jp/?ruby-changes=27443
<znz_v>
biff: [ruby-changes:27448] nobu:r39499 (trunk): * ext/Setup.nt: this file has not been used by default. - http://mla.n-z.jp/?ruby-changes=27448
enebo has joined #ruby-core
schaerli has quit [Remote host closed the connection]
judofyr has quit [Remote host closed the connection]
shirokuro11 has quit [Remote host closed the connection]
takeru has joined #ruby-core
takeru has quit [Ping timeout: 245 seconds]
_protagoras271_ has joined #ruby-core
kosaki8 has quit [Ping timeout: 256 seconds]
ikst has quit [Remote host closed the connection]
schaerli has joined #ruby-core
kosaki2 has joined #ruby-core
ryanf has quit [Quit: leaving]
<znz_v>
biff: [ruby-changes:27449] kosaki:r39501 (trunk): * error.c: clarify a document of SignalException. Process.kill() - http://mla.n-z.jp/?ruby-changes=27449
<zzak>
kosaki2: why is "sleep" necessary in the example?
kosaki2 has quit [Remote host closed the connection]
davidbalbert is now known as davidbalber|away
headius has joined #ruby-core
kosaki2 has joined #ruby-core
<kosaki2>
zzak: for waiting until HUP is delivered.
<kosaki2>
This is current YARV spec. however I don't like this and I would like to improve it later.
<kosaki2>
Counter question. why do you think it deliver immediately? Process.kill() is naturally asynchronous operation.
<kosaki2>
To understand people's expect help an improvement of both implemenation and doc.
takeru has quit [Ping timeout: 260 seconds]
<kosaki2>
One of the answers is, several UNIX has immediate delivery guarantee when signal sent to $$.
<zzak>
kosaki2: one moment
<kosaki2>
However this behavior depend on the spec that the signal which sent by kill($$) handled the sender thread. But Ruby's trap has different semantics.
<kosaki2>
It is handled always main thread.
<kosaki2>
Then, we can not decide to take the exact same semantics.
<zzak>
i would expect it to be delivered immediately as well
<kosaki2>
houwever it is not possible. example, the sender thread is not main thread.
<zzak>
but if that's not the case, and the "sleep" is required to wait for Process.kill operation to finish then it should be documented
<zzak>
since it's "naturally asynchronos operation", i think developers dont know this or realize it
<kosaki2>
I meant, I don't understand why someone think it should be delivered immediately. IOW, current behavior is already documented IMHO.
<zzak>
IOW?
<kosaki2>
in other words
headius_ has joined #ruby-core
<zzak>
where is it documented?
<zzak>
when i see "sleep" in an example, i always wonder why that's being used there
<zzak>
it makes sense once you explained it, but maybe other developers have the same confusion
<zzak>
even just adding a comment in the example: "sleep # wait for Process.kill operation to finish" would be helpful imo
<kosaki2>
Do you have any concrete documentation change idea?
<zzak>
thats my only idea for that example
headius_ has quit [Client Quit]
<zzak>
maybe sleep has better docs
headius has quit [Ping timeout: 252 seconds]
<kosaki2>
When we insert "signal may not be delivered immediately" into a doc of Process.kill(). It lead to make more confusing. Nobody did think it is immediate operation.
<kosaki2>
Ah, makes sense. I like to add a comment to example.
<kosaki2>
Can you commit it?
<zzak>
sure
<zzak>
does my comment make sense?
<kosaki2>
just moment.
<zzak>
np
<kosaki2>
If I was you, I will write "wait that a signal which sent by Process.kill() handled".
<kosaki2>
I meant, "operation" is slightly unclear.
<kosaki2>
In general, signal operation has 2 step.
<kosaki2>
1) sending 2) delivering (aka received by target process)
<kosaki2>
Process.kill() has a guarantee to finish (1), but doesn't have a guarantee (2).
<kosaki2>
This is unix signal rule.
<kosaki2>
Does my explanation make sense?
<zzak>
"wait for receiver to handle signal sent by Process.kill"
<kosaki2>
Good.
<zzak>
makes perfect sense
<zzak>
thank you kosaki-san
<kosaki2>
Thank you too.
schaerli has quit [Remote host closed the connection]
<zzak>
kosaki2: i think your ChangeLog timestamp is messed up again
<zzak>
i will fix i
<zzak>
fix it*
<kosaki2>
Grr, thanks.
<zzak>
np
<znz_v>
biff: [ruby-changes:27450] zzak:r39502 (trunk): * error.c: clarify reason for sleep in SignalException example - http://mla.n-z.jp/?ruby-changes=27450
schaerli has joined #ruby-core
davidbalber|away is now known as davidbalbert
schaerli has quit [Remote host closed the connection]
schaerli has joined #ruby-core
schaerli has quit [Remote host closed the connection]
charliesome has joined #ruby-core
xibbar has joined #ruby-core
kosaki2 has quit [Remote host closed the connection]