MV>
  > I write in C, and when porting some older programs I had written for
  > DOS, I found out that the display routines got messed up. After some
  > testing I found the cause: under OS/2, nothing will be send to the
  > screen until a cr has been send. Until then, the text just stays in a
  > buffer. The solution was to 1) tell OS/2 not to buffer output to the
  > screen, or 2) explicitly flush the buffer after each write.
MV>

  Stop confusing the operating system with the implementation of the
  Standard C Library in your C/C++ compiler.  The buffering of output is
  *nothing* to do with OS/2, and everything to do with IBM CSet++.

  Not all C++ compilers for OS/2 behave in this manner, either.

  > JdeBP <
___
 X MegaMail 2.10 #0:

--- Maximus/2 3.00