From: Randi Botse <nightdecoder@gmail.com>
To: eric@cisu.net
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Division in loop
Date: Wed, 9 Sep 2009 17:12:56 +0700 [thread overview]
Message-ID: <34e1241d0909090312w22fa9d17r18305afa480f8eab@mail.gmail.com> (raw)
In-Reply-To: <200909082157.38271.eric@cisu.net>
No matter i print to unbuffered stderr or stdin, the message will not printed...
whether the loop is quite fast? so there are no chance to printf()
output the message?
On Wed, Sep 9, 2009 at 9:57 AM, Eric Bambach<bot403@cisu.net> wrote:
>
> Wow. I feel silly. Ignore my previous message. It's late here and I missed the
> fflush().
>
next prev parent reply other threads:[~2009-09-09 10:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 14:40 Division in loop Randi Botse
2009-09-08 14:47 ` Saurabh Sehgal
2009-09-08 14:57 ` Bert Wesarg
2009-09-08 14:58 ` Tim Walberg
2009-09-08 15:09 ` Randi Botse
2009-09-09 0:49 ` Glynn Clements
2009-09-09 2:37 ` Randi Botse
2009-09-09 2:39 ` Randi Botse
2009-09-09 2:52 ` Eric Bambach
2009-09-09 2:57 ` Eric Bambach
2009-09-09 10:12 ` Randi Botse [this message]
2009-09-10 0:46 ` Glynn Clements
2009-09-10 7:01 ` Randi Botse
2009-09-10 7:03 ` Manish Katiyar
2009-09-11 7:26 ` Glynn Clements
2009-09-09 0:45 ` Zhenwen Xu
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=34e1241d0909090312w22fa9d17r18305afa480f8eab@mail.gmail.com \
--to=nightdecoder@gmail.com \
--cc=eric@cisu.net \
--cc=linux-c-programming@vger.kernel.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 NNTP newsgroup(s).