[#45910] [ruby-trunk - Bug #6694][Open] Thread.new without block. — "ko1 (Koichi Sasada)" <redmine@...>

24 messages 2012/07/04

[#45913] [ruby-trunk - Bug #6698][Open] MacOSXではDir.globが返すファイル名の内容はUTF8-MACですがencodingがUTF-8になっている — "imkira (Mario Freitas)" <imkira@...>

10 messages 2012/07/04

[#45933] [ruby-trunk - Bug #6716][Open] FileUtils.mv でリンク先がないシンボリックリンクファイルを指定すると ENOENT エラーになる — "tommy (Masahiro Tomita)" <tommy@...>

8 messages 2012/07/10

[#45976] [ruby-trunk - Bug #6756][Open] FileUtils.rm_rf がアクセス権のない空ディレクトリを削除しない — "fumiyas (Fumiyasu SATOH)" <fumiyas@...>

9 messages 2012/07/20

[#46012] [ruby-trunk - Feature #6812][Open] Refactor gc.c — "authorNari (Narihiro Nakamura)" <authorNari@...>

13 messages 2012/07/30

[ruby-dev:45986] Re: [ruby-trunk - Feature #6694] Thread.new without block.

From: SASADA Koichi <ko1@...>
Date: 2012-07-20 14:45:18 UTC
List: ruby-dev #45986
(2012/07/20 22:42), brixen (Brian Ford) wrote:
> I don't think I understand your question. To summarize my objection to this proposed API change: Thread stack size should be something set at the VM level completely outside of Ruby code. Ruby code should not be coupled with implementation details.

I think I understand your question.  And your question should be
discussed on ticket 6695 <https://bugs.ruby-lang.org/issues/6695>.

My proposal is *not* adding "initial stack size parameter for thread
creation".
It is only "configurable thread parameters".  More general framework.

I propose "stack size parameter" at next ticket (using this ticket):
<https://bugs.ruby-lang.org/issues/6695>


This ticket (6694):
  Change Thread.new() API to accept any initial parameters.

Next ticket (6695):
  New parameters including stack size (machine stack size and VM
  stack size).
  Not only stack size, but also "name" and others.
  I think "name" is killer usage of this ticket (6694).

-- 
// SASADA Koichi at atdot dot net


In This Thread