On 12/07/2020 04:01, Luke Mewburn wrote:
On 20-07-12 10:01, Luke Mewburn wrote:
| I propose that the NetBSD C style guide in to /usr/share/misc/style
| is reworded to more explicitly permit braces around single statements,
| instead of the current discourgement.
|
| IMHO,
p...@whooppee.com (Paul Goyette) writes:
>Another +1 here. The "add another statement" is frequently "add a
>debug_printf()" and many is the time i've broken an if statement by
>adding debug code.
{ debug_printf();
}
works and doesn't get forgotten before committing.
I personally find
On 20-07-12 10:01, Luke Mewburn wrote:
| I propose that the NetBSD C style guide in to /usr/share/misc/style
| is reworded to more explicitly permit braces around single statements,
| instead of the current discourgement.
|
| IMHO, permitting braces to be consistently used:
| - Adds
On Sun, 12 Jul 2020, Valery Ushakov wrote:
Luke Mewburn wrote:
I propose that the NetBSD C style guide in to /usr/share/misc/style
is reworded to more explicitly permit braces around single statements,
instead of the current discourgement.
IMHO, permitting braces to be consistently used:
-
Luke Mewburn wrote:
> I propose that the NetBSD C style guide in to /usr/share/misc/style
> is reworded to more explicitly permit braces around single statements,
> instead of the current discourgement.
>
> IMHO, permitting braces to be consistently used:
> - Adds to clarity of intent.
> - Aids
On Sun, Jul 12, 2020 at 10:01:36AM +1000, Luke Mewburn wrote:
> I propose that the NetBSD C style guide in to /usr/share/misc/style
> is reworded to more explicitly permit braces around single statements,
> instead of the current discourgement.
concur
Really, there should always be braces
I propose that the NetBSD C style guide in to /usr/share/misc/style
is reworded to more explicitly permit braces around single statements,
instead of the current discourgement.
IMHO, permitting braces to be consistently used:
- Adds to clarity of intent.
- Aids code review.
- Avoids gotofail:
