From: Paul Van Bellinghen Newsgroups: comp.os.msdos.djgpp Subject: Re: little problem but great troubles Date: Wed, 02 Dec 1998 19:02:31 -0800 Organization: Posted via Supernews, http://www.supernews.com - Discussions start here! Lines: 47 Message-ID: <3665FF46.47309E26@idsi.net> References: <366572DA DOT 75D0D92A AT spektracom DOT de> NNTP-Posting-Host: 208.195.233.107 Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------BD9DC52F828DE9E9FF773AD6" X-Trace: 912643937 N10TIGFEIE96BD0C3C usenet87.supernews.com X-Complaints-To: newsabuse AT supernews DOT com X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com This is a multi-part message in MIME format. --------------BD9DC52F828DE9E9FF773AD6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > some stuff' first appears at the screen when I hit the > key, and then the programm terminates. So, now when I put > a \n behind stuff like > Under DOS, the string probably remains in the output buffer until a terminator (\0,\n,\r,etc.) or a flush of the I/O stream (see fflush()). When the program terminates, the I/O stream is automatically flushed. > > cout << " some stuff\n"; > > it's doing it right. It first shows the line and then - on > keyhit - terminates. > I would be glad if somebody could explain this to me. > Andrej Aderhold --------------BD9DC52F828DE9E9FF773AD6 Content-Type: text/x-vcard; charset=us-ascii; name="pvanbell.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Paul Van Bellinghen Content-Disposition: attachment; filename="pvanbell.vcf" begin:vcard n:Van Bellinghen;Paul x-mozilla-html:FALSE org:Lockheed Martin Fairchild Systems version:2.1 email;internet:pvanbell AT idsi DOT net title:Staff Analyst note:businessl e-mail: paul DOT vanbellinghen AT lmco DOT com x-mozilla-cpt:;0 fn:Paul Van Bellinghen end:vcard --------------BD9DC52F828DE9E9FF773AD6--