I never Finish my programs :(

I got this weird problem that i actualy almost never finish my programs.... when im 80% done i always see somthing that could be added or SHOULD be added to fullfill the programs function

this way i just keep going and keep going and it just gets me insane and eventually i just stop , delete the whole thing and some days later start to make THE SAME application and just stop again with it too....

and i also have a hard time overviewing my program's source, how do u rapidly find the functions u are looking for when u have 1000 lines of code ....

i seriously need some advice here lol.

You can use the search (or find) function.

Split the source code into multiple files, so you won't have 1000 lines of code in one file.

Comment your code, not on whats happening, but on why your doing it.

Oh yeah that seems a good idea :)

Borland's IDEs, like many IDEs, have a neat pane that list all of the functions, templates, and classes in a file, so they are easy to find.

going to get me a borland compiler :D

Make sure to compare with other IDEs. From what I know, Borland has a graphical API that is highly non-portable (read not at all) which makes your code compilable only using Borland which implies that you will have a hard time getting any help at all should you have a problem. You may consider VC05 Express which is free and is much better, in my opinion.

> Borland has a graphical API that is highly non-portable (read not at all) which makes your code compilable only using Borland

That problem is fixed by not using <graphics.h>, just so you know.

Start with a plan of what you want the program to do, then think about how you're going to do it.

Nothing grand to start with, a few notes and a simple class diagram on a couple of sheets of A4 ought to do it. Then implement it and stick to the plan.

If you think "wouldn't this be good..." along the way, then make a note of it for version 2. Resist the temptation to hack it into the design and code it there and then.


Hack it until it breaks doesn't work (as you're finding out).

> Borland's IDEs, like many IDEs, have a neat pane that list all of the functions, templates, and classes in a file, so they are easy to find.
The latest version of Dev-C++ has a "code explorer" as you described. Dev-C++ is released under the fre GNU GPL. So is Code::Blocks; I imagine it has a code explorer as well.

Quote:

---

Originally Posted by Salem

Start with a plan of what you want the program to do, then think about how you're going to do it.

Nothing grand to start with, a few notes and a simple class diagram on a couple of sheets of A4 ought to do it. Then implement it and stick to the plan.

If you think "wouldn't this be good..." along the way, then make a note of it for version 2. Resist the temptation to hack it into the design and code it there and then.


Hack it until it breaks doesn't work (as you're finding out).

---

tnx for the advice:) will do !!