Parenthesize warning #50

Closed
wcaleb opened this Issue Oct 13, 2011 · 7 comments

Comments

Projects
None yet
3 participants

wcaleb commented Oct 13, 2011

When I run boom, I get a series of warnings about parenthesizing arguments for future versions, like this:

/Library/Ruby/Gems/1.8/gems/boom-0.2.3/bin/../lib/../lib/boom/command.rb:198: warning: parenthesize argument(s) for future version
/Library/Ruby/Gems/1.8/gems/boom-0.2.3/bin/../lib/../lib/boom/command.rb:202: warning: parenthesize argument(s) for future version
/Library/Ruby/Gems/1.8/gems/boom-0.2.3/bin/../lib/../lib/boom/storage/keychain.rb:29: warning: parenthesize argument(s) for future version
/Library/Ruby/Gems/1.8/gems/boom-0.2.3/bin/../lib/../lib/boom/storage/keychain.rb:61: warning: parenthesize argument(s) for future version

So should I be wrapping arguments in parentheses? Will not doing so somehow prevent me from updating versions later? And can I hide these warnings in the meantime?

Apologize if this is a CLI newbie question, but I couldn't find the issue addressed anywhere else.

Owner

holman commented Oct 13, 2011

Can you run gem -v and ruby -v on the prompt for me?

wcaleb commented Oct 13, 2011

The first returns 1.3.6, the second 1.86 (2009-06-08 patchlevel 369) [universal-darwin9.0].

I'm running Mac OS X 10.5.8, so I had to do some working around just to update gem in the first place.

wcaleb commented Oct 13, 2011

Oops, that should read 1.8.6.

Owner

holman commented Oct 13, 2011

I suspect this isn't a problem on 1.8.7 (which is what I normally run). I don't think I'll be accommodating 1.8.6 since it's fairly ancient.

@holman holman closed this Oct 13, 2011

wcaleb commented Oct 13, 2011

Fair enough. I don't seem to be having any real problem running boom. Just
wonder if you have ideas about how to hide the warnings so they don't print
every time I run the program?

On Thursday, October 13, 2011, Zach Holman <
reply@reply.github.com>
wrote:

I suspect this isn't a problem on 1.8.7 (which is what I normally run). I
don't think I'll be accommodating 1.8.6 since it's fairly ancient.

Reply to this email directly or view it on GitHub:
#50 (comment)

Owner

holman commented Oct 13, 2011

I'd try updating your Ruby to 1.8.7 or 1.9, to be honest.

arbales commented Oct 14, 2011

its definitely 1.9.2 time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment