&
-
To you, the preprocessor, or the compiler? Where you put spaces, and how many you put, is irrelevant to the compiler as the preprocessor removes them all before sending the tokens to the compiler. Take something like:
#include < stdio.h >
int main( int argc, char **argv )
{
printf("Hello World!\n");
return 0;
}You could have just as easily written it as:
#include < stdio.h >int main( int argc, char **argv ){printf("Hello World!\n");return 0;}The compiler wouldn't have cared. -
No, however
int&is preferable because it makes it clear that the type of "a" is "int&" Yes, you can start a religious argument over this issue. I don't care. I'm right. --Mike-- Ericahist | Homepage | RightClick-Encrypt | 1ClickPicGrabber "You have Erica on the brain" - Jon Sagara to me -
No, however
int&is preferable because it makes it clear that the type of "a" is "int&" Yes, you can start a religious argument over this issue. I don't care. I'm right. --Mike-- Ericahist | Homepage | RightClick-Encrypt | 1ClickPicGrabber "You have Erica on the brain" - Jon Sagara to meMichael Dunn wrote: Ericahist Excellent! I've finally been able to increase my "Pictures of Erica" collection from a measy two to....six. w00t! I suppose six is better than nothing though! :-D Thanks! (been an Erica fan since back the GoogleFight of Erica (yeah!) vs Britney (boo! hiss!)) <insert link to the aforementioned post> :-D I prefer to wear gloves when using it, but that's merely a matter of personal hygiene [Roger Wright on VB] Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. [Rich Cook]