most common errors

what are the most common programming errors you make

mine are

inifinate while loops (forgetting to increment counter var)
forgetting ; in php
misspelling response in asp

I always use too many or too few brackets . I also make a lot of spelling mistakes in variable names. I therefore always make sure I turn notices on in PHP and use Option Explicit in VB.

I sometimes incorrectly declare an overloading protected function, forgetting that it and the original cannot only differ by return type.

How silly of me.

I usually just make silly errors like not puting i = i + 1 when needed etc.

Logic mistakes, when I go back and edit code I forget to retest it.

This usually ends in massive errors (or at least appearing so, I only need to change one line to fix it)

I don't do the little things any more like forgetting the ; in PHP, although I do still sometimes forget that variables start with a $ in PHP. Mainly it's that I don't know how to do something.

Quite a few times I've re-inveted the whell because I didn't know a function existed so I made it from other functions. That's annoying. In things like JavaScript though, it's suprising how much works first time for me. I even made a little search engine thingy which almost worked first time. I had a typo in one place. I fixed that and it worked.

the most common error is my use of vb :p

I don't make misteaks.

Mmmmm...misteak :gurgle:

Quote:

---

Originally posted by MartinLiss
I don't make misteaks.

---

sure you don't, so you are saying you never forgot to put an End If or mispelt a variable:rolleyes:

Quote:

---

Originally posted by rotcrules
sure you don't, so you are saying you never forgot to put an End If or mispelt a variable:rolleyes:

---

That's corect.

I think most of us have made the annoying mistake of not writing a program that we can sell to MS for £10,000,000.

I make that mistake with my every keystroke.

Quote:

---

Originally posted by SteveCRM
the most common error is my use of vb :p

---

Damn. I was going to say something like that when I saw the thread title ;)

Mine's doing silly things like:

Code:

---

for(int i = 0; blah[i] = 4; ++i) { /* ... */ }

---

(the = rather than ==).

haven't seen you round these parts too much. :cool:

Quote:

---

Originally posted by parksie
Damn. I was going to say something like that when I saw the thread title ;)

Mine's doing silly things like:

Code:

---

for(int i = 0; blah[i] = 4; ++i) { /* ... */ }

---

(the = rather than ==).

---

That because you use that silly language.

Now where's my handbag ;)

Trying to program.

Quote:

---

Originally posted by MartinLiss
I don't make misteaks.

---

mmmm misteaks. :rolleyes:

the only mistake i ever make is the when i thought i made a mistake!

Quote:

---

Originally posted by Nightwalker83
mmmm misteaks. :rolleyes:

---

Of corse that was firmly tung in cheak :)

Quote:

---

Originally posted by Nightwalker83
mmmm misteaks. :rolleyes:

---

Dunderpate.

:afrog:

Chit Chat - sometimes I can't tell if it's real or implants :D

How many of you step through code in the immediate window while developing it to see how it behaves?

Or is that too serious a question ;)

Quote:

---

Originally posted by MartinLiss
Of corse that was firmly tung in cheak :)

---

Of course. :rolleyes:

Quote:

---

Originally posted by crptcblade
Dunderpate.

:afrog:

---

Moron. :lol:

Quote:

---

Posted by rotcrules
sure you don't, so you are saying you never forgot to put an End If or mispelt a variable:rolleyes:

---

Em I think its rather hard to mis out an "End If", a } is alot easier to miss than a whole "End If". That reminds me i always forget the ; after the } when creating a class :(.

And now parksie mentions it I always make the mistake of using = when i mean to use ==.
Also for C++ the Variable names are case sensitive so i always make the mistake of just typing them in lower case and expecting the IDE to change the case for me :(.

Quote:

---

Originally posted by szlamany
Chit Chat - sometimes I can't tell if it's real or implants :D

How many of you step through code in the immediate window while developing it to see how it behaves?

Or is that too serious a question ;)

---

All the time.

Quote:

---

Posted by szlamany
How many of you step through code in the immediate window while developing it to see how it behaves?

---

Is that when you use Debug.Print, yea? Well I normally would just use break points but when playing with DirectX breakpoints cause loads of trouble so then I use Debug.Print all the time. :D

BTW does anyone know if C++ has any kind of equivelent to this? Cause I do have to say i really miss it when i use C++ :(.

Forgetting the "New" keyword when instantiating objects in .NET

Quote:

---

Originally posted by parksie
Damn. I was going to say something like that when I saw the thread title ;)

Mine's doing silly things like:

Code:

---

for(int i = 0; blah[i] = 4; ++i) { /* ... */ }

---

(the = rather than ==).

---

:cry: I hate that!! Do it in PHP all the time. Its always great when you do something like,

$user = badperson;
if ($user = goodperson) {
destroyworldfunction();
}

:(

I step-through code ALL THE TIME.

I had no idea before that F8 was "read next line" so I used 50 break points :rolleyes: .

But you know what? I've actually hit into lines of code that work when you step-through but don't if you run-through.

Or they act differently after being compiled.

VERY annoying.

We actually have a DEBUG.PRINT at the top of each and every function, event, sub - everything. I use dual monitors and keep the immediate window fully max'd on the second monitor.

As we run/step/break through code, the trace-path appears in the immediate window.

We have extra DEBUG.PRINT's peppered throughout the code - showing important values/status/etc.

We use F8 and ctrl/shift/F8 (step out of function/sub) extensively.

We also have run into "behaves differently while stepping around in the IDE" vs executable issues. Those are tough bugs to find - DEBUG.PRINT helps the most in those cases.

Quote:

---

Originally posted by alkatran
I step-through code ALL THE TIME.

I had no idea before that F8 was "read next line" so I used 50 break points :rolleyes: .

But you know what? I've actually hit into lines of code that work when you step-through but don't if you run-through.

Or they act differently after being compiled.

VERY annoying.

---

Generally I blame the code running to fast, and find DoEvents will do the trick to slow it down. :)