Re: Wine code comments

2010-06-05 Thread John Voltz
Thanks for all the input. I forgot about using #if (0). That will make life much easier. John

Re: Wine code comments

2010-06-05 Thread James McKenzie
Octavian Voicu wrote: 2010/6/5 James McKenzie : Also if (0)'d code should have a comment block on when and why it was removed and what must be done to re-incorporate it and if someone is working on it, a name and durable contact information. Also, an anticpated completion date, if known, sho

Re: Wine code comments

2010-06-05 Thread Octavian Voicu
2010/6/5 James McKenzie : > Also if (0)'d code should have a comment block on when and why it was > removed and what must be done to re-incorporate it and if someone is working > on it, a name and durable contact information.  Also, an anticpated > completion date, if known, should be entered.  Rel

Re: Wine code comments

2010-06-05 Thread James McKenzie
Frédéric Delanoy wrote: On Sat, Jun 5, 2010 at 05:38, James McKenzie mailto:jjmckenzi...@earthlink.net>> wrote: John Voltz wrote: Hi everyone, I have a question about comments in the Wine code. I noticed while tracking down a bug that a lot of the code comments are

Re: Wine code comments

2010-06-04 Thread Frédéric Delanoy
On Sat, Jun 5, 2010 at 05:38, James McKenzie wrote: > John Voltz wrote: > >> Hi everyone, >> >> I have a question about comments in the Wine code. I noticed while >> tracking down a bug that a lot of the code comments are using the >> block comment marker /*. This is a royal pain when trying to co

Re: Wine code comments

2010-06-04 Thread James McKenzie
John Voltz wrote: Hi everyone, I have a question about comments in the Wine code. I noticed while tracking down a bug that a lot of the code comments are using the block comment marker /*. This is a royal pain when trying to comment out large sections of code where there are a bunch of /* foo */

Re: Wine code comments

2010-06-04 Thread Andrew Nguyen
On Fri, Jun 4, 2010 at 3:35 PM, John Voltz wrote: > Is there are way around it without having to change them all to //? > For private, ad-hoc use, you could possibly use a preprocessor #if 0 block to achieve the desired comment effect.

Re: Wine code comments

2010-06-04 Thread Erich Hoover
On Fri, Jun 4, 2010 at 2:35 PM, John Voltz wrote: > ... > I have a question about comments in the Wine code. I noticed while > tracking down a bug that a lot of the code comments are using the > block comment marker /*. > ... See the wiki page on patches: http://wiki.winehq.org/SubmittingPatches

Wine code comments

2010-06-04 Thread John Voltz
Hi everyone, I have a question about comments in the Wine code. I noticed while tracking down a bug that a lot of the code comments are using the block comment marker /*. This is a royal pain when trying to comment out large sections of code where there are a bunch of /* foo */ comments. Why is th