if you do use sytem("cls"); then you will have to put in time wasting loops or else you won't be able to see much because the system("cls") will clear it all before you get to see it. so in short use some time wasting loops in it if you do use system("cls");
Unfortunately, clearing the screen is impossible to do without platform specificity.
mugenoid, let us know what OS you are using and we'll give you a good solution.
Mr. Cool, unless you are running on hardware as old or older than an AT, it is just way too fast to make coding no-op loops useful. Even then, it is a bad idea, as the OS can do better for just pausing long enough for the user to read the screen...
I agree with Duoas. If you want delays used timed functions like delay() or sleep() or whatever else.
If you are doing a txt game ... the screen can be cleared using clrscr() (conio.h)
If you want a proper screen under DOS, look up Mode13h on the net . You will need a compiler like DJGPP. It's kinda hard to get into that particular mode with std compilers these days .... you have to twiddle with the settings, or use a compiler with protected DOS memory management like DJGPP.
If you are under windows (any), and want to do the rasterization (draw yourself), you should checkout PixelToaster which gives you a frame buffer to play with just like Mode 13 h.
Once you have a frame buffer, you can pretty much do anything ... draw lines, circles , quads etc etc , for any kinda game. ^^