Jeff:
4. Tabs set to four spaces.
Stuart:
4 space good, two space bad?
This sounds like a religious war in the making. So I say 2
spaces for a tab and don't use tab characters. If you can
cleanly fit your code into 80 columns that would also be
nice (though I realize that is unlikely
4. Tabs set to four spaces.
Jeff
4 space good, two space bad?
This sounds like a religious war in the making. So I say 2 spaces for a tab
and don't use tab characters. If you can cleanly fit your code into 80
columns that would also be nice (though I realize that is unlikely for
Palm
That's close to mine. Personally, I'd have it as:
void MyFunc(Char* buffer, UInt32 type)
{
switch(type)
{
case 1:// This is an example with braces.
{
StrCopy(buffer, One);
break;
}
case 2:// This is an example without
On Tuesday 12 August 2003 09:11 pm, Alan Ingleby wrote:
(This is mine...)
void MyFunc(Char* buffer, UInt32 type) {
switch(type) {
case 1:
StrCopy(buffer, One);
break;
case 2:
StrCopy(buffer, Two);
break;
default:
StrCopy(buffer, Huh?);
On a lighter note...
We are trying to standardise our C coding techniques here, and a point of
contention is the layout of a switch statement.
What's the generally preferred way of structuring a switch statement? (This
is mine...)
void MyFunc(Char* buffer, UInt32 type) {
switch(type) {
Jeff Wheeler [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
1. Function definition allows parameters to be commented. I also switched
the order so that inputs were listed first and outputs last.
I've always preferred to have the outputs first, and the inputs last. But
that's just
In a previous post, Alan Ingleby wrote:
What's the generally preferred way of structuring a
switch statement? (This is mine...)
void MyFunc(Char* buffer, UInt32 type) {
switch(type) {
case 1:
StrCopy(buffer, One);
break;
case 2:
StrCopy(buffer, Two);
"Rick Gadbois" [EMAIL PROTECTED] wrote
Does anyone here use design documentation and/or coding standards that are
particularly friendly to the palm/code warrior environment?
p.s. I use WinNT.
The only thing I can suggest is to choose very rigorous and careful
standards and follow t
Does anyone here use design documentation and/or coding standards that are
particularly friendly to the palm/code warrior environment?
p.s. I use WinNT.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
