Date:	Tue, 2 Jun 1998 18:31:25 +0200
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Message-Id:	<199806021631.SAA18725@acp3bf.physik.rwth-aachen.de>
To:	djgpp AT delorie DOT com
Subject:	Re: Gotoxy() Malfunction
Newsgroups:	comp.os.msdos.djgpp
Organization:	RWTH Aachen, III. physikalisches Institut B

In article <199806021459 DOT HAA06099 AT neptune DOT calstatela DOT edu> you wrote:
[...]
> >I'm starting to write short C programs with the djgpp compiler and i've
> >found that gotoxy() function doesn't work well.

It does work, normally (at least it did so far, for all of us). You're
just not using it correctly.

> >After compiling the source code I execute it and :
> >
> >-The cursor's position isn't as I wrote or

Sure of that? What did you learn that from? I.e.: have you *looked* at
the program working (outside RHIDE, preferredly), to check where the
cursor really is?

> >-The cursor's position is O.K. but the printf() function I wrote doesn't
> >appear. 

gotoxy() and printf() *do* *not* work together. Generally spoken,
functions from <conio.h> and <stdio.h> don't work together very well,
if at all. They never did. If you want to printf to the position set
by gotoxy(), use 'cprintf()' (from <conio.h>) instead. For details,
consult the FAQ.

> No, it has to do with the fact that stdio is line buffered. 

Sorry, but this is nonsense. This problem has nothing to do with the
line-buffering issue.

--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -