On Sun, 2008-02-03 at 06:25 +0900, Christian Roese wrote:
> On Feb 2, 2008 1:13 PM, Daniel Brumbaugh Keeney <devi.webmaster / gmail.com>
> wrote:
> 
> > On Feb 2, 2008 11:57 AM, Christian Roese <croese / gmail.com> wrote:
> > > Does anyone know why I can type this at the cmd line:
> > >
> > > /usr/bin/env ruby -w
> > >
> > > and get the correct functionality, but if I use this line in the shebang
> > > line of my .rb files, I get an error from env stating that "ruby -w
> > can't be
> > > found"?  If I change the line to use just ruby (without the -w option),
> > it
> > > works perfectly.  I've seen plenty of programs scattered around the net
> > that
> > > use that same line in a shebang line so I know it should work.
> > >
> > > Any help would be greatly appreciated!
> > >
> > > --
> > > Christian Roese
> >
> > http://en.wikipedia.org/wiki/Shebang_(Unix)#Portability<http://en.wikipedia.org/wiki/Shebang_%28Unix%29#Portability>
> >
> > Daniel Brumbaugh Keeney
> >
> >
> Does this mean I'm hosed on my linux system and I'll have to use either
> 
> /usr/local/bin/ruby -w
> 
> or
> 
> /usr/bin/env ruby  (without the -w switch)
> 
> in my programs?  Is there any way to delimit these args so that env sees
> them as 2 args instead of one whole string?
> 

In short, you're hosed in regards to that particular method. 

Unless I'm mistaken, the shebang line is interpreted by the kernel, and
on Linux it only accepts one parameter to the interpreter the line
defines - so #!/usr/bin/env ruby -w will always call /usr/bin/env with
the parameter "ruby -w", which is not a valid command. There's no way
around this.

If, however, all you need this for is the -w switch to turn on warnings,
just don't do that with a switch to the ruby binary and use the $VERBOSE
global variable to turn warnings on and off. The manpage for ruby even
hints to this:

-w             Enables verbose mode without printing version message at
the beginning.  It sets the $VERBOSE variable to true.

That solution should be more portable.

HTH,

Felix