-
Jul 17th, 2004, 04:31 AM
#1
Thread Starter
Addicted Member
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
-
Jul 17th, 2004, 04:49 AM
#2
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.
-
Jul 17th, 2004, 04:56 AM
#3
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 don't live here any more.
-
Jul 17th, 2004, 05:15 AM
#4
I usually just make silly errors like not puting i = i + 1 when needed etc.
when you quote a post could you please do it via the "Reply With Quote" button or if it multiple post click the "''+" button then "Reply With Quote" button.
If this thread is finished with please mark it "Resolved" by selecting "Mark thread resolved" from the "Thread tools" drop-down menu.
https://get.cryptobrowser.site/30/4111672
-
Jul 17th, 2004, 06:38 AM
#5
Fanatic Member
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)
Don't pay attention to this signature, it's contradictory.
-
Jul 17th, 2004, 06:57 AM
#6
Frenzied Member
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.
Have I helped you? Please Rate my posts.
-
Jul 17th, 2004, 08:47 AM
#7
Frenzied Member
the most common error is my use of vb
-
Jul 17th, 2004, 11:49 AM
#8
-
Jul 17th, 2004, 11:53 AM
#9
Laugh, and the world laughs with you. Cry, and you just water down your vodka.
Take credit, not responsibility
-
Jul 17th, 2004, 11:57 AM
#10
Lively Member
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
[Vbcode]If YourOpinion = WindowsIsCrap Then
Kill Wndows
Open Linux
ElseIf YourOpinion = WindowsIsGreat Then
Unload Me
Else
Get MSNTV
End If[/vbcode]
-
Jul 17th, 2004, 12:01 PM
#11
Originally posted by rotcrules
sure you don't, so you are saying you never forgot to put an End If or mispelt a variable
That's corect.
-
Jul 17th, 2004, 12:31 PM
#12
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.
I don't live here any more.
-
Jul 17th, 2004, 12:37 PM
#13
Monday Morning Lunatic
Originally posted by SteveCRM
the most common error is my use of vb
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 ==).
I refuse to tie my hands behind my back and hear somebody say "Bend Over, Boy, Because You Have It Coming To You".
-- Linus Torvalds
-
Jul 17th, 2004, 01:18 PM
#14
Frenzied Member
haven't seen you round these parts too much.
-
Jul 17th, 2004, 01:21 PM
#15
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.
-
Jul 17th, 2004, 04:13 PM
#16
Monday Morning Lunatic
Now where's my handbag
I refuse to tie my hands behind my back and hear somebody say "Bend Over, Boy, Because You Have It Coming To You".
-- Linus Torvalds
-
Jul 17th, 2004, 06:44 PM
#17
Fanatic Member
-
Jul 17th, 2004, 07:00 PM
#18
Originally posted by MartinLiss
I don't make misteaks.
mmmm misteaks.
when you quote a post could you please do it via the "Reply With Quote" button or if it multiple post click the "''+" button then "Reply With Quote" button.
If this thread is finished with please mark it "Resolved" by selecting "Mark thread resolved" from the "Thread tools" drop-down menu.
https://get.cryptobrowser.site/30/4111672
-
Jul 17th, 2004, 07:31 PM
#19
Lively Member
the only mistake i ever make is the when i thought i made a mistake!
[Vbcode]If YourOpinion = WindowsIsCrap Then
Kill Wndows
Open Linux
ElseIf YourOpinion = WindowsIsGreat Then
Unload Me
Else
Get MSNTV
End If[/vbcode]
-
Jul 17th, 2004, 07:42 PM
#20
Originally posted by Nightwalker83
mmmm misteaks.
Of corse that was firmly tung in cheak
-
Jul 17th, 2004, 07:46 PM
#21
Originally posted by Nightwalker83
mmmm misteaks.
Dunderpate.
Laugh, and the world laughs with you. Cry, and you just water down your vodka.
Take credit, not responsibility
-
Jul 17th, 2004, 08:02 PM
#22
Chit Chat - sometimes I can't tell if it's real or implants
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
-
Jul 17th, 2004, 09:08 PM
#23
when you quote a post could you please do it via the "Reply With Quote" button or if it multiple post click the "''+" button then "Reply With Quote" button.
If this thread is finished with please mark it "Resolved" by selecting "Mark thread resolved" from the "Thread tools" drop-down menu.
https://get.cryptobrowser.site/30/4111672
-
Jul 17th, 2004, 10:01 PM
#24
Ex-Super Mod'rater
When your thread has been resolved please edit the original post in the thread ( )
and amend "-[RESOLVED]-" to the end of the title and change the icon to , Thank you.
When posting Code use the [VBCode]Code Here[/VBCode] tags to be able to use the code highlighting.
-
Jul 17th, 2004, 10:27 PM
#25
Originally posted by szlamany
Chit Chat - sometimes I can't tell if it's real or implants
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.
-
Jul 17th, 2004, 10:33 PM
#26
Ex-Super Mod'rater
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.
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++ .
When your thread has been resolved please edit the original post in the thread ( )
and amend "-[RESOLVED]-" to the end of the title and change the icon to , Thank you.
When posting Code use the [VBCode]Code Here[/VBCode] tags to be able to use the code highlighting.
-
Jul 18th, 2004, 12:29 AM
#27
Frenzied Member
Forgetting the "New" keyword when instantiating objects in .NET
Being educated does not make you intelligent.
Need a weekend getaway??? Come Visit
-
Jul 18th, 2004, 05:28 AM
#28
PowerPoster
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 ==).
I hate that!! Do it in PHP all the time. Its always great when you do something like,
$user = badperson;
if ($user = goodperson) {
destroyworldfunction();
}
-
Jul 18th, 2004, 09:30 AM
#29
Fanatic Member
I step-through code ALL THE TIME.
I had no idea before that F8 was "read next line" so I used 50 break points .
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.
Don't pay attention to this signature, it's contradictory.
-
Jul 18th, 2004, 09:42 AM
#30
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.
-
Jul 19th, 2004, 12:40 AM
#31
PowerPoster
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 .
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.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|