From owner-freebsd-hackers  Mon Jun  2 00:58:43 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id AAA05684
          for hackers-outgoing; Mon, 2 Jun 1997 00:58:43 -0700 (PDT)
Received: from iceberg.anchorage.net. (root@iceberg.anchorage.net [207.14.72.150])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA05678
          for <hackers@FreeBSD.ORG>; Mon, 2 Jun 1997 00:58:39 -0700 (PDT)
Received: from aak.anchorage.net (ai-131 [207.14.72.131]) by iceberg.anchorage.net. (8.6.11/8.7.3) with SMTP id WAA06392; Sun, 1 Jun 1997 22:55:23 -0800
Date: Sun, 1 Jun 1997 23:47:50 -0800 (AKDT)
From: Steve Howe <un_x@anchorage.net>
X-Sender: abc@aak.anchorage.net
To: Michael Smith <msmith@atrad.adelaide.edu.au>
cc: freebsd-hackers <hackers@FreeBSD.ORG>
Subject: Re: signed/unsigned cpp
In-Reply-To: <199706010645.QAA12329@genesis.atrad.adelaide.edu.au>
Message-ID: <Pine.BSF.3.95q.970601234203.1753D-100000@aak.anchorage.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sun, 1 Jun 1997, Michael Smith wrote:

> Because neither is equivalent to the "default" signedness.
> 
> const char * is _not_ equivalent to const unsigned char *, or const
> signed char *.

i would appreciate it if you could explain further - why?
any char * can _only_ be signed or unsigned, even if it's
the default that makes it so. ?
-------------------------------------------------------------------------
 Sleep: a sign a caffeine deprivation ... http://www.anchorage.net/~un_x
-------------------------------------------------------------------------