Forum: Ruby-core [ruby-trunk - Bug #7380][Open] benchmark/driver.rb: --executables separator

Issue #7380 has been reported by Eregon (Benoit Daloze).

----------------------------------------
Bug #7380: benchmark/driver.rb: --executables separator
https://bugs.ruby-lang.org/issues/7380

Author: Eregon (Benoit Daloze)
Status: Open
Priority: Normal
Assignee:
Category:
Target version:
ruby -v: ruby 2.0.0dev (2012-11-17 trunk 37693) [x86_64-darwin10.8.0]


Hello,

The separator used between ruby executables for the benchmark/driver.rb 
script is ";".
This requires the argument to be quoted (at least in bash/zsh) and 
produce an unintuitive result if not: only the first executable is taken 
by the script, the second executable launches the ruby interpreter with 
no arguments, thus waiting on stdin, which feels like the benchmark 
script hangs.

I proposed to use ":", the standard path separator instead.
For compatibility, ";" could split too, but I wish to document ":" in 
the help.

What do you think? May I go ahead?

Issue #7380 has been updated by mame (Yusuke Endoh).

Status changed from Open to Assigned
Assignee set to ko1 (Koichi Sasada)
Target version set to 2.0.0

ko1, what do you think?

--
Yusuke Endoh <mame@tsg.ne.jp>
----------------------------------------
Bug #7380: benchmark/driver.rb: --executables separator
https://bugs.ruby-lang.org/issues/7380#change-33810

Author: Eregon (Benoit Daloze)
Status: Assigned
Priority: Normal
Assignee: ko1 (Koichi Sasada)
Category:
Target version: 2.0.0
ruby -v: ruby 2.0.0dev (2012-11-17 trunk 37693) [x86_64-darwin10.8.0]


Hello,

The separator used between ruby executables for the benchmark/driver.rb 
script is ";".
This requires the argument to be quoted (at least in bash/zsh) and 
produce an unintuitive result if not: only the first executable is taken 
by the script, the second executable launches the ruby interpreter with 
no arguments, thus waiting on stdin, which feels like the benchmark 
script hangs.

I proposed to use ":", the standard path separator instead.
For compatibility, ";" could split too, but I wish to document ":" in 
the help.

What do you think? May I go ahead?

Issue #7380 has been updated by ko1 (Koichi Sasada).


I always use -e with quote strings.  does it bother you?

By the way, -e accept `:'
 like -e "foo::path1; bar::path2"
as a label of path.

----------------------------------------
Bug #7380: benchmark/driver.rb: --executables separator
https://bugs.ruby-lang.org/issues/7380#change-33925

Author: Eregon (Benoit Daloze)
Status: Assigned
Priority: Normal
Assignee: ko1 (Koichi Sasada)
Category:
Target version: 2.0.0
ruby -v: ruby 2.0.0dev (2012-11-17 trunk 37693) [x86_64-darwin10.8.0]


Hello,

The separator used between ruby executables for the benchmark/driver.rb 
script is ";".
This requires the argument to be quoted (at least in bash/zsh) and 
produce an unintuitive result if not: only the first executable is taken 
by the script, the second executable launches the ruby interpreter with 
no arguments, thus waiting on stdin, which feels like the benchmark 
script hangs.

I proposed to use ":", the standard path separator instead.
For compatibility, ";" could split too, but I wish to document ":" in 
the help.

What do you think? May I go ahead?

Issue #7380 has been updated by Eregon (Benoit Daloze).


ko1 (Koichi Sasada) wrote:
> I always use -e with quote strings.  does it bother you?
>
> By the way, -e accept `:'
>  like -e "foo::path1; bar::path2"
> as a label of path.

Oh, right, I did not think to the name::path usage, it would be weird to 
have both : and ::.

I like the solution to pass multiple -e options, thank you!
----------------------------------------
Bug #7380: benchmark/driver.rb: --executables separator
https://bugs.ruby-lang.org/issues/7380#change-33954

Author: Eregon (Benoit Daloze)
Status: Closed
Priority: Normal
Assignee: ko1 (Koichi Sasada)
Category:
Target version: 2.0.0
ruby -v: ruby 2.0.0dev (2012-11-17 trunk 37693) [x86_64-darwin10.8.0]


Hello,

The separator used between ruby executables for the benchmark/driver.rb 
script is ";".
This requires the argument to be quoted (at least in bash/zsh) and 
produce an unintuitive result if not: only the first executable is taken 
by the script, the second executable launches the ruby interpreter with 
no arguments, thus waiting on stdin, which feels like the benchmark 
script hangs.

I proposed to use ":", the standard path separator instead.
For compatibility, ";" could split too, but I wish to document ":" in 
the help.

What do you think? May I go ahead?