Date: Mon, 24 Jan 2000 16:45:11 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Petr Maxa <maxa AT sse-za DOT sk>
cc: djgpp AT delorie DOT com
Subject: Re: signed - unsigned chars
In-Reply-To: <004401bf664a$8324bfe0$0307028a@prmivv03>
Message-ID: <Pine.SUN.3.91.1000124164351.12997D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 24 Jan 2000, Petr Maxa wrote:

> The problem is solved, but is not as neat as I would expect, because I still
> have to mix signed and unsigned types when I use libc functions like printf,
> sprintf in the case, that the unsigned type is readable text and need to be
> printed or when the buffers may use both text and binary (unsigned)
> information.

Why did you need to mix signed and unsigned when using library 
functions?  Are there any specific problems?  There shouldn't be:
AFAIK, the library functions are 8-bit clean.  If you know about
any problems, please report them here.