From: "Schwartz, Barry" <Barry.Schwartz@netapp.com>
To: "'Kyle Boon'" <kboon@bmi.osu.edu>, pthreads-win32@sources.redhat.com
Subject: RE: Simple question.
Date: Wed, 21 Aug 2002 12:11:00 -0000 [thread overview]
Message-ID: <6440EA1A6AA1D5118C6900902745938E0514FB1D@black.eng.netapp.com> (raw)
If it were me...
I would create another thread that manged an output queue. I would arrange for the contributing threads to write their output to this thread's input method -- as one "atomic" text block. Then I would call some other method to "print" it or queue it up for printing. The management of sending chars to the screen would be done by this queue manager and it would be the only place I would put an output call in all of my code. Also, I would consider alternatives to cout if you have any.
-----Original Message-----
From: Kyle Boon [mailto:kboon@bmi.osu.edu]
Sent: Wednesday, August 21, 2002 12:03 PM
To: pthreads-win32@sources.redhat.com
Subject: Simple question.
I'm not sure if this is the right place for my question - so I apolgize in
advance if it not.
First some quick background. I am a college undergrad charged with porting a
linux app to the win32 platform. I chose this pthreads implementation to make
the task much easier. So far it's worked very well. My only question is how
people deal with console output. I have multiple threads using cout to print
things to the console, but the output is all jumbled up. If I try to link
with a thread safe version of the standard library on windows, I get all
sorts of linker errors. It seems like people must have had to work around
this before, but I haven't been able to find any information about it.
Any help would be greatly appreciated.
Kyle Boon
next reply other threads:[~2002-08-21 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-21 12:11 Schwartz, Barry [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-21 12:02 Kyle Boon
2002-08-21 14:59 ` Wayne Robin Isaacs
2002-08-21 15:22 ` Wayne Robin Isaacs
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=6440EA1A6AA1D5118C6900902745938E0514FB1D@black.eng.netapp.com \
--to=barry.schwartz@netapp.com \
--cc=kboon@bmi.osu.edu \
--cc=pthreads-win32@sources.redhat.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).