var arg

'Its legal to have other parameters in a method that uses a var arg.'
does the above statement means

please explain.

Singh Himanshu wrote:'Its legal to have other parameters in a method that uses a var arg.'
does the above statement means
"void dostuff(int... x, int... y){}"

please explain.

http://lmgtfy.com/?q=java+varargs+tutorial

Varargs should be the last parameter

Singh Himanshu wrote:'Its legal to have other parameters in a method that uses a var arg.'
does the above statement means
"void dostuff(int... x, int... y){}"

please explain.

the var-args will always be the last.

and also not both the args in the method are var-args.

Singh Himanshu wrote:'Its legal to have other parameters in a method that uses a var arg.'
does the above statement means
"void dostuff(int... x, int... y){}"

please explain.

Yes, definitely more than one parameters can exist with one var-args in a method but one and only limitation is var-args must be the last parameter in the method declaration.

Vishal Kashyap wrote:
Yes, definitely more than one parameters can exist with one var-args in a method but one and only limitation is var-args must be the last parameter in the method declaration.

No...we can only have one var-args argument in a method, and that should be the last.
more then one var-args will give compile time error as "too-many var-args"

shanky sohar wrote:. . . No...we can only have one var-args argument in a method, and that should be the last. . . .

That is the same as the previous poster said.

Singh Himanshu, welcome to JavaRanch

Campbell Ritchie wrote:

shanky sohar wrote:. . . No...we can only have one var-args argument in a method, and that should be the last. . . .

That is the same as the previous poster said.

hmmm..Yes,you are right..last time i am not able to understand that.

and moreover, isnt int..x,int...y redundant?!
int...x itself means any number of int parameters.
infinity+infinity=infinity => so why not just use 'infinity' once

And what about foo(String ... words, int ... numbers) . . .? That is also prohibited by the rule about one varargs parameter.

Vinoth Kumar Kannan wrote:and moreover, isnt int..x,int...y redundant? . . .

No it isn't; it is simply impossible to tell which the last int for x is and which the first int for y is.

Campbell Ritchie wrote:No it isn't; it is simply impossible to tell which the last int for x is and which the first int for y is.

Thats a reason why Java prevented more than 1 var-args for a method.
What I wanted to say was...
int... x => any number of integers
int... y => any number of integers
Even if more than 1 var-arg was allowed for a method, you wouldn't want to use int... x,int... y , because int... x simply means the same and would satisfy the requirement as well.

Vinoth Kumar Kannan wrote:and moreover, isnt int..x,int...y redundant?!

No. For the method there is a real difference between x and y. So int... x, int... y is definitely not the same as int... xy.

Multiple varargs may sometimes be easy to detect (like String... s, int... i), but in too many cases (e.g. Object... o, String... s -- any String is also an object) there is just too much ambiguity. That's why only one is allowed.