🔒 Locked

Most common syntax error

Started by Eskhan Apr 26, 2003 at 3:45 PM 42 replies 1.8k views

Original Post

Eskhan

Apr 26, 2003 at 3:45 PM

What is your most common syntax error?

The one my compiler catches most often is too few paranthesises in large function calls

Zipster

511

Zipster

Apr 26, 2003 at 3:57 PM

The compiler rarely catches any syntax errors, because I usually find and fix any as I''m writing the code and before it is compiled, however I have to say I remember getting a lot of errors resulting from mis-typing variable or function names.

Enigma1625

Apr 26, 2003 at 4:01 PM

Yeah simple typos are usually what cause the mose errors for me. I''ve come to realize not to panic when after compiling a simple bit of code I get 76 errors, because I know that most likely I just mispelled something

unkn.Enigma1625

masonium

Apr 26, 2003 at 4:01 PM

missing a semicolon or an #endif in a header file

Agentidd

Apr 26, 2003 at 4:20 PM

;

-DD

downward_spiral

Apr 26, 2003 at 4:28 PM

Getting the case wrong in variable names such as aBigLongVariableName, or spelling them wrong when I go back to a class I wrote months ago.

walkingcarcass

Apr 27, 2003 at 3:33 AM

Unrolling a loop 64 times by copy-paste, then finding 64*n typos

********

A Problem Worthy of Attack
Proves It''s Worth by Fighting Back

Eskhan

Author

Eskhan

Apr 27, 2003 at 5:28 AM

hehe, ouch

Dire.Wolf

Apr 27, 2003 at 7:10 AM

Forgetting to put the leading/trailing underscore on a member variable:

myMemberVariable_

Then I''ll do something like:

myMemberVariable.Foo();

When I''m programming late at night sometimes I''ll screw up my if-statements when testing for equality... = instead of ==

Eskhan

Author

Eskhan

Apr 27, 2003 at 12:03 PM

quote:

When I''m programming late at night sometimes I''ll screw up my if-statements when testing for equality... = instead of ==

guuh, just mentioning that makes my head hurt, i remember once when i had c++ homework and i was running really short on time, i spent probably over and hour trying to find out why the hell my program wouldn''t work, then i catch a = instead of a == in an if statement, damn i was so stressed out

BrownBean

Apr 27, 2003 at 12:13 PM

I''ve seen someone do this, then took hours debugging:


for ( int x = 0; x < 10; x++ );  // not the semi colon shouldn''t be there
  printf ( "Number: %d\n", x );

// output, only once instead of 10 times...
"Number: 0

I agree with the "=" once instead of "==", still make that error.

Peon

102

Peon

Apr 27, 2003 at 12:23 PM

I don''t really make me syntzx error anymore, but then again, the things I''m working on now are pretty simplistic. I would say the most common one for me right now would be writing the wrong thing for an argument that calls for a pointer. I end up with a lot of "paramter 2 cannot be converted to type blah blah" syntax errors, when working with pointers.

CraZeE

Apr 27, 2003 at 12:31 PM

void funcName(void); <-- Ouch
{
}

quant

Apr 27, 2003 at 12:36 PM

Utwo

Apr 27, 2003 at 1:20 PM

The thing I hate about using ''='' instead of ''=='' in an if() statement, is that using ''='' is perfectly valid. It just does something other than what you want it to. Haha.

Eskhan

Author

Eskhan

Apr 27, 2003 at 3:12 PM

Yeah, at least you should get a warning
or something

Spudder

Apr 27, 2003 at 4:19 PM

Its gotta be semi-colons for me, 95% of my errors are missing semi-colons which i never seem to notice until i compile.

cowsarenotevil

478

cowsarenotevil

Apr 27, 2003 at 4:22 PM

I do the = instead of == a lot, and I also always make mistakes with variables in nested for loops.

-~-The Cow of Darkness-~-

eldee

Apr 27, 2003 at 4:32 PM

mine usually result from undescriptive iterators in nested loops..
a while back i used to get alot of errors related to cyclic depenency

-eldee
;another space monkey;
[ Forced Evolution Studios ]

Do NOT let Dr. Mario touch your genitals. He is not a real doctor!

Blaste

Apr 27, 2003 at 4:42 PM

I would have to say... semicolons, either I forget them, or I put them where they don''t need to be. The Borland compiler I use warns you about the == and = things in if structures, which is awesome and has saved me a few times

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.