From: "Eregon (Benoit Daloze)" <redmine@...>
Date: 2012-07-27T23:42:16+09:00
Subject: [ruby-core:46817] [ruby-trunk - Feature #6793] easier ability to "run as the currently running ruby"


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


naruse (Yui NARUSE) wrote:
> Eregon (Benoit Daloze) wrote:
> > Currently, I work around it by using `ps -o args -p pid` and GetCommandLineA(), which is far from optimal when we know it's so easily accessible for the VM (argc/args).
> 
> argv[0] is not reliable on some environment.
> See also my comment on #4046.

I meant args to get the VM flags (args[1..argc-1]).

I'm fine using RbConfig for getting the path to the ruby binary for the moment.
I admire your effort to try to solve it without RbConfig.

Sorry for discussing of #6648 here, I should have answered on that thread.
----------------------------------------
Feature #6793: easier ability to "run as the currently running ruby"
https://bugs.ruby-lang.org/issues/6793#change-28491

Author: rogerdpack (Roger Pack)
Status: Feedback
Priority: Normal
Assignee: 
Category: 
Target version: 


Hello all.  I couldn't remember if this had been requested before or not but...

It would be kind to be able to do:
current_ruby = OS.ruby_bin
system("#{current_ruby} another_file.rb")

And thus guarantee execution of a sub-file using the same ruby executable.

Today we have
system("#{Gem.ruby} another_file.rb")

but I'd like to have something available without loading full rubygems.

Python equivalent: sys.executable

Suggestion:
>> OS.ruby_bin # or OS.executable, etc.
=> "C:/installs/Ruby193p194/bin/ruby.exe"
or
>> RbConfig.???
=> "C:/installs/Ruby193p194/bin/ruby.exe"

Thanks.
-roger-


-- 
http://bugs.ruby-lang.org/