On Sat, Jun 5, 2010 at 05:38, James McKenzie <span dir="ltr"><<a href="mailto:jjmckenzie51@earthlink.net">jjmckenzie51@earthlink.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div class="h5">John Voltz wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi everyone,<br>
<br>
I have a question about comments in the Wine code. I noticed while<br>
tracking down a bug that a lot of the code comments are using the<br>
block comment marker /*. This is a royal pain when trying to comment<br>
out large sections of code where there are a bunch of /* foo */<br>
comments. Why is this allowed? Is there are way around it without<br>
having to change them all to //?<br>
<br>
</blockquote></div></div>
Simple answer: We use 'c' comment convention because some compilers choke on the C++ style.<br>
<br>
You could use #if (0) and should use this to mark out possible locations for buggy code as it was noted elsewhere. Using /* and */ is not good coding practice to comment out code.<br><font color="#888888">
<br> James McKenzie<br>
</font></blockquote><div><br></div><div>> (E. Hoover)<br>>Particularly, the section entitled "Avoid C++, C99 and non-portable C<br>>constructs."<br></div><div><br></div><div>Actually, aside from debugging functions, and stuff in headers files, "if (0)" would be more portable than "#if 0", with the additional advantage that it leads to less code rot, since obsolete code tends to be deleted earlier, and not simply forgotten.</div>
<div><br></div><div>Besides, it shouldn't incur any runtime penalty, since "if (0)" blocks are typically discarded at compile time.</div><div><br></div><div>What do you think about it?</div><div><br></div><div>
Frédéric</div>