From: thales@virtualbs.com.br
To: gcc-help@gcc.gnu.org
Subject: Re: \n to \r\n in stdout
Date: Mon, 07 Nov 2005 13:03:00 -0000 [thread overview]
Message-ID: <1131368607.436f509fdd6f4@webmail.virtualbs.com.br> (raw)
Well,
After 15 days of trying to get an answer for how the outputed file was being
corrupted and how to fix it, in 30 minutes my problem was solved here.
The setmode() function solved my problem. I didn't use it up to now because all
my references, including cplusplus.com doesn't have any citation of this
function.
Thanks a lot to Ingo Krabbe and even more to Eljay John, for this simple
resolution of my problem.
Even programming games using Allegro and SDL, programming in lots of languages
and programming lots of applications for a large company here in Brazil, I
can't get where you all are, but one day I'll be here to help people like you
all do!
Gratefully again,
Thales Medeiros.
Citando John Love-Jensen <eljay@adobe.com>:
> Hi Thales,
>
> I did not realize you were using C-style input/output.
>
> Try this before using stdout for anything else:
> setmode(fileno(stdout), O_BINARY);
>
> HTH,
> --Eljay
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
next reply other threads:[~2005-11-07 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 13:03 thales [this message]
2005-11-07 13:08 ` John Love-Jensen
2005-11-07 13:17 ` thales
-- strict thread matches above, loose matches on Subject: below --
2005-11-07 12:40 thales
2005-11-07 12:52 ` John Love-Jensen
2005-11-07 12:08 thales
2005-11-07 12:24 ` John Love-Jensen
2005-11-07 12:41 ` Ingo Krabbe
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=1131368607.436f509fdd6f4@webmail.virtualbs.com.br \
--to=thales@virtualbs.com.br \
--cc=gcc-help@gcc.gnu.org \
/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).