# GetoptLong

**URL:** <https://www.ruby-forum.com/t/getoptlong/113322>\
**Category:** Ruby\
**Created:** [August 29, 2007, 8:19pm UTC](https://www.ruby-forum.com/t/getoptlong/113322 "2007-08-29T20:19:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bill\_Saunders](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/eb9ed0/32.png) [@Bill\_Saunders](https://www.ruby-forum.com/u/Bill_Saunders)\
**Post date:** [August 29, 2007, 8:19pm UTC](https://www.ruby-forum.com/t/getoptlong/113322/1 "2007-08-29T20:19:35Z")

</div>

I am new to this mailing. I have some users who are fed up with the  
following warning and my inability to explain and/or remove it. It  
occurs on every call to GetoptLong.new, and yes, it is on windows.

H:/work/i2cc.rb:1140: warning: don’t put space before argument  
parenthese

If anyone could provide some help, it would be greatly appreciated.

Bill Saunders  
Wave7 Optics, Inc

---

<div class="post-metadata">

**Author:** ![Bill\_Saunders](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/eb9ed0/32.png) [@Bill\_Saunders](https://www.ruby-forum.com/u/Bill_Saunders)\
**Post date:** [August 29, 2007, 8:26pm UTC](https://www.ruby-forum.com/t/getoptlong/113322/2 "2007-08-29T20:26:37Z")

</div>

Alle mercoledì 29 agosto 2007, Bill Saunders ha scritto:

> Wave7 Optics, Inc  
> It means that you’ve called a method, put its arguments in parentheses  
> and put  
> a space between the method name and the opening parentheses. Something  
> like  
> this:

irb: 003\> puts (1, 2)  
(irb):3: warning: don’t put space before argument parentheses

Stefano

---

<div class="post-metadata">

**Author:** ![Bill\_Saunders](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/eb9ed0/32.png) [@Bill\_Saunders](https://www.ruby-forum.com/u/Bill_Saunders)\
**Post date:** [August 29, 2007, 8:32pm UTC](https://www.ruby-forum.com/t/getoptlong/113322/3 "2007-08-29T20:32:40Z")

</div>

Bill Saunders wrote:

> Wave7 Optics, Inc

It may help if you could include (inline, not attached) some code  
examples  
(shorted to the minimal) of the code executed from the program(s) in  
question  
and how they are being used, e.g. .\foo.rb --file bar.txt. In my  
experience it  
can generally be best that way for people to know whats going on.

In the past I’ve usually used optparse (which I dislike) or rolled my  
own  
argument hunt & peck. After reading this and looking up getoptlong, it  
looks  
much more to my tastes so I’ll definitely have to check out. Thanks for  
a poke  
hehe;-)

TerryP.