That ought to be balanced with "don't screw up the revision history, people use it". It's one thing to reformat code that is unreadable, for the most part this code didn't come close to unreadable.
Granted.
I wasn't suggesting that. I was saying
if (expr) statement; // OK
The test and the statement run together visually, which is it is preferred to put the statement on the following line.
The exception I was saying was reasonable is if you are doing something like
if (!pointer) return (-EINVAL);
Short, sweet, readable, no worries.
return is not a function ;-)
Jeff
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
