Date: Sun, 27 Aug 2000 08:49:14 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Radical NetSurfer <radsmail AT juno DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: printf, cprintf and CR/LF problem
In-Reply-To: <s2fgqs8iobmdvbfrjfl2tfm57i2o9e2mov@4ax.com>
Message-ID: <Pine.SUN.3.91.1000827084655.3086C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sat, 26 Aug 2000, Radical NetSurfer wrote:

> Todays latest discoveries, with no work-around to date:
> 
> Apparently, 
>   printf
>  and
>   cprintf
> 
> are immediately outputting a cr/lf, and scrolling, once it reaches the
> line limit, before it may actually be necessary to do so (issue cr/lf
> and scrolling).

The behavior you see in printf is in the BIOS.  The behavior you see in 
cprintf is for compatibility with what Borland does.

> Is there any way to get this proper (and apparently expected) behavior
> from printf, and cprintf, in DJGPP and other compilers?

You could remove the \n from the format, and print it at the beginning of 
the next line instead.