Getting the context through the view that's passed in the onClick method instead of taking it through the constructor.

Isn't it a little better to get the context from the view that's passed in as parameter to the onClick method instead of taking it through the constructor and storing it as a member variable?

I think it makes for a cleaner code and maybe less prominent to crashes. I've read in some discussions on stackoverflow and some articles that passing the context around isn't always a great idea and could lead to memory leaks or something like that. I don't fully grasp those concepts yet, but I think I'd go for taking it from the view unless some other issues apply for that way of accessing it as well :).

This is what I'm talking about:

public void onClick(View view) {
            String time = timeLabel.getText().toString();
            String temperature = temperatureLabel.getText().toString();
            String summary = summaryLabel.getText().toString();
            String message = String.format("At %s it will be %s and %s",
                    time,
                    temperature,
                    summary);
            Toast.makeText(view.getContext(), message, Toast.LENGTH_LONG).show();
        }

The view that's passed in is the RelativeLayout from the hourly_list_item.xml and its context is the HourlyForecastActivity, so it works in the same way.

And we don't do any changes to the HourAdapter constructor, don't add a context member variable in HourAdapter to be set in the constructor, and don't change the call to the HourAdapter constructor from the HourlyForecastActivity class.

Can anyone share their opinion and pros and cons of getting the context in these two different ways?