[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#50658: Error messages including function names violates coding conve
From: |
Eli Zaretskii |
Subject: |
bug#50658: Error messages including function names violates coding conventions |
Date: |
Tue, 28 Sep 2021 15:28:59 +0300 |
> From: Stefan Kangas <stefan@marxist.se>
> Date: Tue, 28 Sep 2021 05:11:23 -0700
> Cc: 50658@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> +Invalid input''. This convention is better avoided in most cases.
> >
> > That last sentence is unexpected, and seems to contradict everything
> > you wrote before it. Which convention should be avoided, and why?
>
> To be honest, I was a bit unsure about this sentence. I guess I'm
> trying to say "don't overdo it" or "don't do it by default just because
> you can".
>
> But perhaps this is already clear from the rest of the text?
Yes, I think it is.
- bug#50658: Error messages including function names violates coding conventions, (continued)
- bug#50658: Error messages including function names violates coding conventions, Stefan Kangas, 2021/09/18
- bug#50658: Error messages including function names violates coding conventions, Eli Zaretskii, 2021/09/18
- bug#50658: Error messages including function names violates coding conventions, Stefan Kangas, 2021/09/27
- bug#50658: Error messages including function names violates coding conventions, Eli Zaretskii, 2021/09/28
- bug#50658: Error messages including function names violates coding conventions, Stefan Kangas, 2021/09/28
- bug#50658: Error messages including function names violates coding conventions,
Eli Zaretskii <=
- bug#50658: Error messages including function names violates coding conventions, Stefan Kangas, 2021/09/28