This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
RE: fopen() and CON
- To: <cygwin at sourceware dot cygnus dot com>
- Subject: RE: fopen() and CON
- From: "Andre Oliveira da Costa" <costa at cade dot com dot br>
- Date: Fri, 10 Dec 1999 20:07:41 -0200
> From: cygwin-owner@sourceware.cygnus.com
> [mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Chris Faylor
> Sent: Friday, December 10, 1999 7:25 PM
> To: Andre Oliveira da Costa
> Cc: Cygwin
> Subject: Re: fopen() and CON
[...]
> It depends on what you mean by "should". If it was up to me, the answer
> would be "no". If it is up to Microsoft, the answer is "yes". Cygwin
> can't override the underlying OS.
I agree with you: IMHO, fopen("CON.xxx", "w") should _not_ open the terminal
device (CON). But, thanks to Micro$oft, WYEINWYG (What You Expect Is Not
What You Get). I understand that Cygwin is bound to the underlying OS,
which, unfortunately, is a s* one. You guys are doing a _great_ job, keep it
going =)
> I'm not aware of any way to override this. I suppose that on NT you
> could open the file in POSIX mode, but cygwin has no way of doing this
> via fopen.
Yeah, never mind... I've already tweaked my program to write to
FILENAME_.html instead of FILENAME.html (so that it will generate CON_.html
instead of CON.html). I just wanted to check it out because there might have
been a chance I was forgetting something really basic, or it could be some
problem with Cygwin.
Thanks a lot for your attention.
Best regards,
Andre
--
André Oliveira da Costa
(costa@cade.com.br)
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com