Edit Question - KnowledgeHub

Title Body

What are the reasons that Google use varargs for the parameters in the AsyncTask ? For example the methods execute() , doInBackground() and publishProgress() all use the [Type]... notation. I think that makes it "harder" to use so they must have some good reasons which I overlooked? So, either we have no parameters, one or many parameters. Let's break it down: No parameters (easy): Params parameter is Void and that's it. (The methods cannot use it... so that's pretty safe.) One parameter : Here, I at least, feel the need to make a check at the beginning of the doInBackground() method. For example, here is a task receiving an Integer and producing a result of type Double : public Double doInBackground(Integer... myParameters) { // we are only expecting one parameter if (myParameters.length != 1) throw new IllegalArgumentException("!= 1"); return 100d * myParameters[0]; } More than one parameter . Now here must be where Google made the right choice? But as I see it's either you are interested in a list of parameters of the same type , or you want different types of parameters. Google only addressed one of these cases (with different types you need some kind of common interface. In man

Tags (comma-separated) Cancel