On Tue, Jan 23, 2001 at 10:07:10AM -0500, Jonathan Earle wrote:
> > /*
> > * I tend to find standard C comments easier to read. They stand out,
> > * especially for multiple lines (although I always try to put the :end:
> > * on a separate line for clarity).
> > */
>
> I like this style for multiple line comments, but prefer the '//' for single
> liners. Two less characters to type after all. :)
and potentially no end of weird problems if you have mac users editing
your code... suddenly a compiler may ignore the rest of a file starting
at a given // or # comment, and you'll find its caused by their
different linebreaks. had this problem with php. havent seen it with C
yet. does gcc handle non-correct^H^H^H^H^H^H^Hunix linebreaks now? it
didnt when i used djgpp all those years ago.
// are nicer on the eyes, for short comments. and death to capital
// letters. and oooh, vim auto-extends // comments, thats handy isn't
// it! :-]
j.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
