# Why does Ruby issue this warning?

**URL:** <https://rubytalk.org/t/why-does-ruby-issue-this-warning/14467>\
**Category:** ruby-talk\
**Created:** [28 October 2004 19:33 UTC](https://rubytalk.org/t/why-does-ruby-issue-this-warning/14467 "2004-10-28T19:33:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Curt\_Hibbs3](https://avatars.discourse-cdn.com/v4/letter/c/2acd7d/32.png) [@Curt\_Hibbs3](https://rubytalk.org/u/Curt_Hibbs3)\
**Post date:** [28 October 2004 19:33 UTC](https://rubytalk.org/t/why-does-ruby-issue-this-warning/14467/1 "2004-10-28T19:33:13Z")

</div>

This line of code:

&nbsp;&nbsp;puts HTTP.get url("collection", MARK)

results in this warning message:

&nbsp;&nbsp;warning: parenthesize argument(s) for future version

Of course, heeding the warning and changing the code to:

&nbsp;&nbsp;puts HTTP.get(url("collection", MARK))

eliminates the message. But does anyone know why this is happening?

Curt

---

<div class="post-metadata">

**Author:** ![Bill\_Atkins](https://avatars.discourse-cdn.com/v4/letter/b/c4cdca/32.png) [@Bill\_Atkins](https://rubytalk.org/u/Bill_Atkins)\
**Post date:** [28 October 2004 22:07 UTC](https://rubytalk.org/t/why-does-ruby-issue-this-warning/14467/2 "2004-10-28T22:07:43Z")

</div>

I think Matz is trying to deprecate the use of multiple method calls  
without parentheses, since they can cause ambiguity, e.g.:

&nbsp;&nbsp;myfunc a b, c

Is it a(b) being passed with c to myfunc, or is a(b, c) being passed to myfunc?

Bill

> **···**
>
> On Fri, 29 Oct 2004 04:33:13 +0900, Curt Hibbs \<curt@hibbs.com\> wrote:
> 
> > This line of code:
> > 
> > &nbsp;&nbsp;puts HTTP.get url("collection", MARK)
> > 
> > results in this warning message:
> > 
> > &nbsp;&nbsp;warning: parenthesize argument(s) for future version
> > 
> > Of course, heeding the warning and changing the code to:
> > 
> > &nbsp;&nbsp;puts HTTP.get(url("collection", MARK))
> > 
> > eliminates the message. But does anyone know why this is happening?
> > 
> > Curt