From owner-freebsd-questions Thu Jan 31 8:21:23 2002 Delivered-To: freebsd-questions@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 7FB6D37B400 for ; Thu, 31 Jan 2002 08:21:19 -0800 (PST) Received: from [212.238.194.207] (helo=tanya.raggedclown.net) by post.mail.nl.demon.net with esmtp (Exim 3.33 #1) id 16WJxe-00008Q-00 for freebsd-questions@freebsd.org; Thu, 31 Jan 2002 16:21:18 +0000 Received: by tanya.raggedclown.net (tanya.raggedclown.intra, from userid 500) id F218C44F6F; Thu, 31 Jan 2002 17:21:16 +0100 (CET) Date: Thu, 31 Jan 2002 17:21:16 +0100 From: Cliff Sarginson To: freebsd-questions@freebsd.org Subject: Re: unsigned char portability Message-ID: <20020131162116.GB1512@raggedclown.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.24i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jan 31, 2002 at 02:47:47PM +0000, June Carey wrote: > Hi, > > I have a question I was hoping someone could answer. > Does the "unsigned char" C type have any machine architecture portability > problems ? If you explicitly "unsign" it no I believe not..as long as you don't play silly buggers with it inside a struct. The signedness of a plain char is architecture/compiler dependent. Which is a pain in the a*se. -- Regards Cliff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message