--- Comment #12 from Stewart Gordon <>  2009-07-14 10:23:04 PDT 
(In reply to comment #11)
> I've switched the error message to "both auto and explicit type given". auto
> class C {} will still trigger the "storage class has no effect" one though. I
> don't think error messages of this kind are avoidable if you want to make
> directly applying inapplicable storage classes an error.

Probably 99% of poorly written error messages can be improved if only one stops
to think about it.

How about "auto cannot be applied to classes" or "auto can only be applied to
variable declarations"?  We could use the same format for all illegal uses of

Of course, the relevance of this to auto'll change when/if the grammar change
proposed in comment 9 is implemented....

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to