Mail Archives: djgpp/2002/02/14/11:01:41
On Thu, 14 Feb 2002, CBFalconer wrote:
> cprintf avoids the blowups, but seems to pay no attention to
> '\n'. The output has line feeds, without <cr>.
That's normal behavior: the \n -> CR-LF conversion only happens for file
I/O. With direct screen I/O, you need to put the \r there explicitly.
> Using it also brings in a long startup delay.
It shouldn't, but perhaps leave this alone for now (debugging more than
one problem at once is not a good idea ;-).
> I changed the output strings to terminate in \r\n, and now I get
> bright patches of blue on the screen, with no output!
Does your program call some conio functions to set the screen colors? If
not, you should have see the normal white on black output from cprintf.
Can you show the fragment which calls cprintf?
- Raw text -