Date:	Tue, 7 Dec 1999 00:49:14 -0500 (EST)
From:	Jude Dashiell <jdashiel AT clark DOT net>
To:	djgpp AT delorie DOT com
Subject:	Re: gcc and ansi.sys question
In-Reply-To:	<384BA38C.639879AD@gs707.com>
Message-ID:	<Pine.GSO.4.05.9912070045340.22938-100000@shell.clark.net>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

I don't use cprintf() since cprintf() will not speak on my screen reader
software.  Though the program is being compiled for a largely sighted
audience of other astrologers, the programmer is totally blind and the
screen reader software is mandatory.  The fflush(stdout) alternative
following printf() without "\n" as the ends of their lines is a reasonable
sacrifice in this case. On Mon, 6 Dec 1999, Alexey Zakhlestine wrote:

> 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>
> 

--------------------

jude <jdashiel AT clark DOT net>

- Raw text -