It means that the while loop will continue until the integer value of ch is 13.
If you look at line 9, you can see that the value of ch is set to the return value of the function getch(). I believe this is a 3rd-party function which prompts the user to enter a character with the keyboard, and returns the value of the character.
So, the loop repeats until the user enters a character whose value is 13.
If you look at an ASCII value table (e.g. http://www.asciitable.com/) you'll see that 13 corresponds to a carriage return. So, basically, this loop continues until the user hits Enter.
Isn't the clrscr() also bad coding habits since its slower and a security risk, or does that only apply to system("cls")? Also in place of the clear screen you would use some form of output manipulation? Just want to know since I am a beginner and trying to learn to iron out bad habits.
@gobiking clrscr() is part of the non-standard <conio.h> library.
Its use is discouraged as it isn't available in all compilers, and even those which have a conio.h library may not offer the same functions, or they may not work in the same way.
In other respects it is ok, it is fast and there are no security risks. The downside is that if you share your code with others, it may not work, or if you upgrade to a different compiler, it may not work.
There are alternatives, such as using the Winapi functions, or a library such as ncurses.