Re: POSIX and getch(), clrscr()
On Jul 20, 11:30 am, Michele 'xjp' <mich...@removethis.nectarine.it>
wrote:
I am using a POSIX-compliant system, Cygwin on Windows.
This is the first I've heard that Cygwin is Posix compliant.
I need the features of conio.h's getch() and clrscr(), but I
can't compile programs with #include <conio.h> (since conio.h
is NOT POSIX).
Is there away to implement clrscr() and getch() ?
Traditionally, under Unix, they are part of the curses library.
(I don't think this is Posix, but rather an Open Systems
extension to Posix.) Versions are available for Windows (under
the name ncurses, I think), so you can use it more or less
portably.
PS: a C++ program POSIX-compliant with advantages have? "Only"
portability? Any drawbacks?
The Windows Posix-compliant layer is only there for the show;
from what I hear, it's not really usable. The CygWin toolset
runs significantly slower than anything else under Windows
(including UWin or MSys), and I suspect (although I've not
verified) that this is due to some Unix-like intermediate layer.
In general, you can suppose that native Windows will run better
(faster, more reliably) under Windows than any Unix-like
emulation, and that native Unix will run better under Unix than
any Windows like emulation. The basic functionalities of the
two systems are, however, very, very similar (except maybe for
some of the threading primitives---although recent versions of
Windows also have Posix-like conditional variables), so it is
relatively simple to define a neutral interface, implement it
for both systems, and use it. In no case would I try to do
Posix under Windows (or vice versa).
--
James Kanze (Gabi Software) email: james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34