I think argument parsing is important for things like opening files
using a shoes app, and for other applications interacting with shoes.
A thought: Would be kind of cool if you could 'shoes somescript.shy/
thar/be/a/url!' and have it open to it's '/thar/be/a/url!' page. :)
On 10/09/2008, at 5:41 PM, Cecil Coupe wrote:
On Tue, 2008-09-09 at 23:50 -0700, Martin DeMello wrote:
I know - it's just that its argv handling is inconsistent with
respect
to ruby's with what seems like no very good reason.
I'm not an apologist or combative, just a developer who has had to to
parse the command line. Shoe's has it's own switches (-h, --gem x y
z ... ) that it needs to parse first. Being a cross platform GUI app,
I'm wondering how the argument parsing should work in Shoes, in
Windows.
Actually, I'm wondering if it has to work at all. It is a GUI, no?
--Cecil
martin
On Tue, Sep 9, 2008 at 11:38 PM, Cecil Coupe <[EMAIL PROTECTED]>
wrote:
Shoes doesn't use your installed Ruby. It's its own thing, not an
addition to your Ruby. A different, local, 'shoes' variety of Ruby
with
different rules.
On Tue, 2008-09-09 at 22:53 -0700, Martin DeMello wrote:
$ cat testargv.rb
p ARGV
$ shoes testargv.rb
["testargv.rb"]
$ ruby testargv.rb
[]
$ shoes testargv.rb -1
invalid option: -1
$ ruby testargv.rb -1
["-1"]
