bison-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: type-clash diagnostic wording consistency


From: Akim Demaille
Subject: Re: type-clash diagnostic wording consistency
Date: 03 Nov 2002 17:54:17 +0100
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter)

| reader.c generates these two diagnostics:
|   type clash (`T1' `T2') on default action
|   result type clash on merge function F: `T1' vs. `T2'
| 
| It's better if we use consistent wording, so I changed the wording of
| the latter to:
| 
|   result type clash (`T1' `T2') on merge function F

honestly, I prefer the other one: we often have error messages that
are ``constant before the colon, and then a changing part after the
colon┬┤┬┤.  In between quotes, because it's not written down, but merely
the common framework, AFAICS.  Parentheses are not common in my error
message catalogue :)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]