Hi Alan,
I have so far been using the /* ... */ for most, if not all, my C code.
The reason being that it was C, not C++. As all compilers that are
relevant to me are indeed accepting this by default, I have no objection
whatsoever to adopting //. In fact, it makes it much clearer what is and
what
Hi, Alan,
On Jan 21, 2010, at 22:39 , Alan W. Irwin wrote:
>> I certainly find the // comments convenient, but I recently ran
>> into a small annoyance on a project with a manually maintained
>> Makefile. I found that I needed to use the gcc compiler option...
>>
>> -std=gnu99
>>
>> ...in or
On 2010-01-21 21:08-0800 David MacMahon wrote:
> Hi, Alan,
>
> On Jan 21, 2010, at 14:03 , Alan W. Irwin wrote:
>
>> Certainly, the C99 standard supports the
>> // style of comments in C code as does gcc. Is anyone here aware of
>> any modern C compiler that does not understand the // form of com
Hi, Alan,
On Jan 21, 2010, at 14:03 , Alan W. Irwin wrote:
> Certainly, the C99 standard supports the
> // style of comments in C code as does gcc. Is anyone here aware of
> any modern C compiler that does not understand the // form of comment?
I certainly find the // comments convenient, but I
This post concerns what style we should adopt for our multiline comments. I
think most people agree that using /* ... */ for commentary is a poor idea
(see, for example, the discussion of the missing trailing */ issue below).
Thus, for C++ we should probably drop the /* */ form of commentary
altoge
