From: Erik Veenstra <google@...>
Date: 2005-01-19T01:36:04+09:00
Subject: Re: Ignoring RUBYOPT ?

> > The problem with RUBYOPT is easily solved in the Linux
> > universe by executing a shell script in which RUBYOPT is
> > set to nothing before launching Ruby. There are no
> > irritating DOS-box popping up here. (It wouldn't be called
> > "DOS-bos", anyway...) The problem is really a problem in
> > the Windows world. And it's exactly the latter that has no
> > execve...
>
> You can do it as `env -u RUBYOPT'.
>
> And, FreePascal can't call Windows APIs? If possible,
> SetEnvironmentVariable() would be usable.

Doing system calls on a high level was one of the options I had
in mind. It is possible, but system calls are always OS
specific. EEE, like it is today, can be compiled on Linux,
Darwin and Windows, with the same (functional) result. That's
nice, I want to keep it that way.

If there were no working alternative, I could do it. But the
previous mentioned solution with the bootstrapping script (pure
Ruby) does work.

I'll concentrate on the bootstrapping solution right now.
Thanks.

gegroet,
Erik V.