From: Mumit Khan <khan@nanotech.wisc.EDU>
To: "cygwin@sourceware.cygnus.com" <cygwin@sourceware.cygnus.com>
Subject: Re: Getting simple STL program to compile
Date: Thu, 23 Sep 1999 00:37:00 -0000 [thread overview]
Message-ID: <199909230736.CAA22103@mercury.xraylith.wisc.edu> (raw)
In-Reply-To: <GGENGIKFAAIPAAAA@my-deja.com>
" Clark Sims " <clarksimsgnu@my-Deja.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@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: Mumit Khan <khan@nanotech.wisc.EDU>
To: "cygwin@sourceware.cygnus.com" <cygwin@sourceware.cygnus.com>
Subject: Re: Getting simple STL program to compile
Date: Thu, 30 Sep 1999 23:42:00 -0000 [thread overview]
Message-ID: <199909230736.CAA22103@mercury.xraylith.wisc.edu> (raw)
Message-ID: <19990930234200.NyByahyk7pEiZJcKpOfc1q-94hwph7H7D4XjEmZdtaU@z> (raw)
In-Reply-To: <GGENGIKFAAIPAAAA@my-deja.com>
" Clark Sims " <clarksimsgnu@my-Deja.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@sourceware.cygnus.com
next prev parent reply other threads:[~1999-09-23 0:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-22 17:32 Clark Sims
1999-09-23 0:37 ` Mumit Khan [this message]
1999-09-30 23:42 ` Mumit Khan
1999-09-30 23:42 ` Clark Sims
-- strict thread matches above, loose matches on Subject: below --
1999-09-23 6:17 Earnie Boyd
1999-09-30 23:42 ` Earnie Boyd
1999-09-17 20:31 Earnie Boyd
1999-09-30 23:42 ` Earnie Boyd
1999-09-17 6:28 Clark Sims
1999-09-30 23:42 ` Clark Sims
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199909230736.CAA22103@mercury.xraylith.wisc.edu \
--to=khan@nanotech.wisc.edu \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).