Mail Archives: cygwin/1999/09/23/03:38:40
" Clark Sims " <clarksimsgnu AT my-Deja DOT com> writes:
>
> This is rather unsettling. Don't the programmers at Cygnus test for STL funct
> ionality?
STL works just fine. Why would "Cygnus" test for features that are
specific to Microsoft runtime? If I remember correctly, you are
using conio.h and getch(), which are not part of UNIX/POSIX nor
standard C++, so Cygwin obviously doesn't support it.
There is no conio.h in Cygwin, nor will there be a conio.h in Cygwin in
the future.
And, contrary to what you believe, getch is not a "Unix" function. There
is a getch in curses, but that's obviously not what you're looking for
here.
Mixing win32-specific getch and C++ streams is also a very bad idea. Your
use of fflush(NULL) seems odd -- you can't portably "flush" input streams.
> This is such a big part of where C++ programming is heading.
As I mention earlier, STL works just fine. You need to learn what is STL
and what is not STL before making such statements.
> Isn't this basicly the whole compiler. Wouldn't it have been easier to just c
> hange the path? Why download cygwin at all?
If you're going to use POSIX functionality, perhaps mingw32 port is what
you need.
http://www.xraylith.wisc.edu/~khan/software/gnu-win32/
while you're there, also check mno-cygwin howto to see how -mno-cygwin
really works.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -