--- Comment #11 from Christian Kamm <>  
2009-07-14 09:35:40 PDT ---
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.

By the way, bug 3118 would benefit from having a list of attributes and
declarations that should trigger an error if combined via direct application. I
can't guarantee I'll find the time to work on it though.

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

Reply via email to