From:	Alexey Zakhlestine <alx AT gs707 DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: gcc and ansi.sys question
Date:	Mon, 06 Dec 1999 14:52:45 +0300
Organization:	MTU-Intel ISP
Lines:	31
Message-ID:	<384BA38C.639879AD@gs707.com>
References:	<Pine DOT GSO DOT 4 DOT 05 DOT 9912051432440 DOT 28045-100000 AT shell DOT clark DOT net>
NNTP-Posting-Host:	dial52232.mtu-net.ru
Mime-Version:	1.0
X-Trace:	gavrilo.mtu.ru 944481173 6007 195.34.52.232 (6 Dec 1999 11:52:53 GMT)
X-Complaints-To:	usenet-abuse AT mtu DOT ru
NNTP-Posting-Date:	6 Dec 1999 11:52:53 GMT
X-Mailer:	Mozilla 4.7 [en] (Win95; I)
X-Accept-Language:	ru
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

try using "cprintf " instead of "printf"

Jude Dashiell wrote:

> I wrote some code and compiled it using gcc and found I must have been
> doing things incorrectly with screen control since results for sighted
> users were unuseable.  A short relevant sample of the code follows:
> #include <stdio.h>
> #include <conio.h>
>
> row=2;
> col=30;
> gotoxy(row,col);
> printf("natal chart locator");
> row=4;
> col=3;
> gotoxy(row,col);
> printf("astrological");
>
> My guess is that stdio.h and conio.h are fighting.  I'd like to do things
> in such a way as to avoid conflict, so does gcc have ansi screen control
> functions outside of conio.h that can replace gotoxy()?
> Since I use a screen reader when I work with gcc it's essential I avoid
> any extra cprintf() functions since those write to the screen in such a
> way as to mess output up very badly.  Specifically the screen output
> sounds jumbled.
>
> --------------------
>
> jude <jdashiel AT clark DOT net>

- Raw text -