>you need to use the system() command for clear screen
Just because it's available doesn't mean you should use it. There are three big reasons not to use system for this: Security, portability, and performance. You would do better to write your own screen clearing function using the Win32 API than to use system.

>I would like to state that running a program in a DOS window without the occasional claer screen will be quite messy
I would like to retort that clearing the screen when your program starts is antisocial because it removes all output from prior programs. I don't imagine you would be thrilled to have data that you intended to use for reference wiped out because some moron wanted things to look cleaner. If you're running from an IDE then clearing the screen at program start is stupid because it does nothing. The console window is empty to begin with.

>and a clear screen just helps to keep it clean and neat.
Who are you to judge whether a console that you don't own needs to be kept clean and neat? If you do own the window then by all means clear the screen if you think it improves life, but you only prove your idiocy by doing it on a fresh window. Really the only valid reason for clearing the console window in programs like these is for showing cute attention getters like paging menus and animation. There are better tools for such things, so you're only arguing in favor of cluelessness. And did I mention that there's absolutely no way to clear the screen portably?

>It doesn't make you an antisocial prick.
Clearly you've never been on the receiving end of a screen clear and had critical data wiped out. Therefore you're in no position to defend the newbies of the world.

>Callign somebody that based on a clearscreen use is just ignorant
No offense, but you seem to be the ignorant one in this case. You decided to champion a bad practice when you were unaware of the issues involved.

>no offense.
None taken, you made an honest try.