Thread: conio.h functions in mingw?

DevC++ versions 4.80 and 4.992 do define conio.h in the compiler library. Although clrscr() is more of a Borland compiler function.

You can use system("cls") to clear the screen if you get desperate but thats not really good advise as system commands are bad and unsafe, There are windows funtions that clear the screen... dev does use the windows.h header library so a windows function is a much safer way to do this

Here's a few functions that I've cobbled together.

Code:

void GotoXY(int x, int y)
{
  COORD coord;
  coord.X = x;
  coord.Y = y;
  SetConsoleCursorPosition(GetStdHandle(STD_OUTPUT_HANDLE), coord);
}

void GetXY(int *x, int *y)
{
  CONSOLE_SCREEN_BUFFER_INFO  csbInfo;
  GetConsoleScreenBufferInfo(GetStdHandle(STD_OUTPUT_HANDLE), &csbInfo);
  *x = csbInfo.dwCursorPosition.X;
  *y = csbInfo.dwCursorPosition.Y;
}
...
void ClrEol() 
{
	int i;
	int x, y;
	COORD a = { 80, 1 };
	COORD b;
	SMALL_RECT r;
	DWORD len;
	CHAR_INFO str[81];
	for(i = 0; i < 80; i++) {
		str[i].Char.AsciiChar = ' ';
		str[i].Attributes     = 0x07;
	}
	GetXY(&x, &y);
	len = 80 - x;
	b.X = 0;
	b.Y = 0;
	r.Top = y;
	r.Left = x;
	r.Bottom = y+1;
	r.Right = (SHORT)(x + len);
	WriteConsoleOutput(GetStdHandle(STD_OUTPUT_HANDLE), str, a, b, &r);
}

void ClrLine(int y)
{
	GotoXY(0, y);
	ClrEol();
}

void ClrScr(void)
{
	COORD a = {0,0};
	DWORD nwrite;
	FillConsoleOutputAttribute(GetStdHandle(STD_OUTPUT_HANDLE), 0x07, 2000, a, &nwrite);
}

Not saying that these are the best way to do things, but as far as I can tell, it works.
Obviously, it's an ugly hack to use constant 2000 in ClrScr.

--
Mats

If I remember right, delay is a "sleep for x ms", which is what Windows Sleep does:
http://msdn2.microsoft.com/en-us/library/ms686298.aspx

--
Mats

Eh, I tried using #include<windows> and used sleep(100), but it says that
" 'sleep' undeclared (first use this function)"
Bummer...Now what?
@matsp - Im quite the C++ noob, didnt get a word of your indegenious functions...

Originally Posted by ultrabot90

Eh, I tried using #include<windows> and used sleep(100), but it says that
" 'sleep' undeclared (first use this function)"
Bummer...Now what?
@matsp - Im quite the C++ noob, didnt get a word of your indegenious functions...

Try Sleep instead of sleep - remember, C (and thus C++) is a case-sensitive language, so upper and lower case names aren't the same.

My "indegenious" functions are just calls to various Windows system calls - you can look up the system calls in MSDN if you like. If there's anything in the calls you find unclear, please ask.

--
Mats

System calls are unsafe and hackable. You can use cin.get() in C++ or in C use getchar()

The main problems with system() are that it is unportable and unsafe.

It's unportable because you don't know if a given system has the command that you're invoking. For example, there's no such command as PAUSE on UNIX systems, so if a system("PAUSE") call was executed on such a system, at best, nothing would happen.

It's unsafe because you don't know exactly what it is that you're executing. If you used system("ls"), and someone created an executable called ls in a location in the path before the real ls, their ls would be executed. This ls could do anything. It could create a security hole.

There are other problems with system(): for example, it uses the user's default shell. If this shell is customized or incompatible with the shell you were expecting, there could be problems.

It's best to simply avoid system() if possible, and in the case of keeping a Windows console open it's certainly possible.

It's unsafe because you don't know exactly what it is that you're executing. If you used system("ls"), and someone created an executable called ls in a location in the path before the real ls, their ls would be executed. This ls could do anything. It could create a security hole.

I think this is rather theoretical though. If the user's system has been compromised so badly, chances are you cannot really make it very much worse. After all, the user himself/herself might have invoked a planted executable on their way to using your program.

Writing safe code is a habit, not an afterthought based on the supposed runtime environment.

If you avoid risky constructs from the outset, then your code will be better when it matters.

Whats PDCurses?

Public Domain Curses

And whats gcc/g++?

gcc is a C compiler, g++ is its C++ counterpart, and both are part of GCC. I am not entirely sure what entropyrexor means though, since on Windows gcc and g++ are available mainly either by the MinGW port, or Cygwin.