< :前の番号
^ :番号順リスト
> :次の番号
P :前の記事
N :次の記事（スレッド移動）
|<:スレッドの先頭
>|:次のスレッド
^ :返事先
_:自分への返事
>:同じ返事先を持つ記事（前）
<:同じ返事先を持つ記事（後）
---:分割してスレッド表示、再表示
| :分割して（縦）スレッド表示、再表示
~ :スレッドのフレーム消去
.:インデックス
..:インデックスのインデックス
2013/4/7 KOSAKI Motohiro <kosaki.motohiro / gmail.com>:
> Also, Process.exit! escape to run at_exit handler. I think exit! is too drastic.
> it help many situation than flushing, but also makes much side effect. I suspect
> "fork { print "a" }" type output lost makes lots test-all break.
We can flush stdout (and stderr).
Because they are flushed just before fork, flush on child and parent
is harmless.
This doesn't solve problems about other objects, though.
Of course, there is a less-drastic document-only solution:
"Use exit! in forked child process to avoid dual finalization."
> Instead of, providing fork callback likes pthread_atfork() and uses it?
I'm not sure how such calllback is used.
--
Tanaka Akira