--- Megamax Printf bug ---

Thread View: net.micro.atari16

4 messages

[T] Back to Threads [V] Tree View [G] Group Articles

4 total messages Started by nep.pgelhausen Wed, 26 Mar 1986 23:25

#275

Author: nep.pgelhausen
Date: Wed, 26 Mar 1986 23:25

9 lines
1010 bytes

Despite Jwahar R. Bammi's rebuttal, the problem described (no printing
of statements not  ending in '\n' until explicit buffer flush) is a bug.
It is possible to use fflush(stdout) to get around it, as he describes,
but that is not how most standard library printf()s require things.
Sorry, Jwahar.
			-Richard Hartman
			nep.pgelhause@ames-vmsb
------

Re: --- Megamax Printf bug ---

#308

Author: robert
Date: Thu, 27 Mar 1986 23:19

10 lines
1072 bytes

> Despite Jwahar R. Bammi's rebuttal, the problem described (no printing
> of statements not  ending in '\n' until explicit buffer flush) is a bug.
> It is possible to use fflush(stdout) to get around it, as he describes,
> but that is not how most standard library printf()s require things.

No, no.  I have yet to see any printf do any automatic buffer flushing
on micros, minis, or main frames.
Jwahar was right!

Robert J. Drabek

Re: --- Megamax Printf bug ---

#316

Author: Erik Freed
Date: Sat, 29 Mar 1986 20:28

19 lines
1471 bytes

> > Despite Jwahar R. Bammi's rebuttal, the problem described (no printing
> > of statements not  ending in '\n' until explicit buffer flush) is a bug.
> > It is possible to use fflush(stdout) to get around it, as he describes,
> > but that is not how most standard library printf()s require things.
> 
> No, no.  I have yet to see any printf do any automatic buffer flushing
> on micros, minis, or main frames.
> Jwahar was right!

I have only seen this behavior on one out of about 5 machines I have worked
on. Since, I believe, this is not documented in K&R (and in most Unix manuals) 
the nomer of "bug" does seem correct. It is just a widespread and familiar 
one...
-- 
-------------------------------------------------------------------------------
                           Erik James Freed
			   Aurora Systems
			   San Francisco, CA
			   {dual,ptsfa}!aum!freed

Re: --- Megamax Printf bug ---

#311

Author: Tainter
Date: Mon, 31 Mar 1986 15:16

13 lines
1120 bytes

> 
> Despite Jwahar R. Bammi's rebuttal, the problem described (no printing
> of statements not  ending in '\n' until explicit buffer flush) is a bug.
> It is possible to use fflush(stdout) to get around it, as he describes,
> but that is not how most standard library printf()s require things.
> Sorry, Jwahar.
> 			-Richard Hartman
> 			nep.pgelhause@ames-vmsb
Really?  Most of the printf()s I have experienced have had this "feature".

The "bug" is not in printf().  The bug is in the OS where you cannot set a NOT
BUFFERED flag.
--j.a.tainter

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads