On Mon, May 18, 2020 at 9:20 PM Gregory Nutt wrote:
>
> > ... Either way, the left edge of the comment will not line up
> > with the "define" or "undef."
>
> This is the perfect illustration of the problem of mixing the
> incompatible C and pre-processor indentation. Visually, you eye is
> drawn
... Either way, the left edge of the comment will not line up
with the "define" or "undef."
This is the perfect illustration of the problem of mixing the
incompatible C and pre-processor indentation. Visually, you eye is
drawn to want to align the C code with the pre-processor indentation
So, would the correct indentation for the comment be at 2 columns or at 4
columns here? Either way, the left edge of the comment will not line up
with the "define" or "undef."
Column 1. Why should there be any indentation on the comments. There is
no C nesting at all.
It is nearly impossi
On Mon, May 18, 2020 at 8:08 PM Gregory Nutt wrote:
>
> > Actually, I just ran into another nxstyle-related conundrum and I
> > don't see anything about this in the coding standard.
> >
> > Regarding indentations, the coding standard says that everything is
> > indented by units of 2, so that all
Actually, I just ran into another nxstyle-related conundrum and I
don't see anything about this in the coding standard.
Regarding indentations, the coding standard says that everything is
indented by units of 2, so that all C code begins at column 4n + 2.
But preprocessor statements begin with
Actually, I just ran into another nxstyle-related conundrum and I
don't see anything about this in the coding standard.
Regarding indentations, the coding standard says that everything is
indented by units of 2, so that all C code begins at column 4n + 2.
But preprocessor statements begin with a '
