Dominik Vogt [EMAIL PROTECTED] writes:
On Sat, Jul 10, 2004 at 06:42:24PM +1000, Scott Smedley wrote:
* Please put single statements in loops or if clauses in curly
braces, i.e.
=20
if (1)
{
foo;
}
=20
not
=20
if (1)
On Sun, Jul 11, 2004 at 11:19:55AM -0400, Dan Espen wrote:
Dominik Vogt [EMAIL PROTECTED] writes:
On Sat, Jul 10, 2004 at 06:42:24PM +1000, Scott Smedley wrote:
* Please put single statements in loops or if clauses in curly
braces, i.e.
=20
if (1)
{
Hi Dominik, :)
To avoid problems with comiling / reading the fvwm sources, please
* adhere to the ANSI-C 88 standard, not the new one.
Specifically,
- Don't use C++-like comments with //
- Declare variables only at the beginning of a block.
* limit your lines to 79
* Please put single statements in loops or if clauses in curly
braces, i.e.
if (1)
{
foo;
}
not
if (1)
foo;
What's the rationale behind this? I must confess I'm not particularly fond
of this restriction but I will, of course,
Scott Smedley [EMAIL PROTECTED] writes:
* Please put single statements in loops or if clauses in curly
braces, i.e.
if (1)
{
foo;
}
not
if (1)
foo;
What's the rationale behind this? I must confess I'm not
On Sat, Jul 10, 2004 at 06:42:24PM +1000, Scott Smedley wrote:
* Please put single statements in loops or if clauses in curly
braces, i.e.
if (1)
{
foo;
}
not
if (1)
foo;
What's the rationale behind this? I must
To avoid problems with comiling / reading the fvwm sources, please
* adhere to the ANSI-C 88 standard, not the new one.
Specifically,
- Don't use C++-like comments with //
- Declare variables only at the beginning of a block.
* limit your lines to 79 characters (if possible, do not
