Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: C++ features for C Date: Tue, 15 May 2018 10:23:55 -0700 Organization: None to speak of Lines: 25 Message-ID: References: <11edbfd7-461d-4579-8ac7-a9e84a6b7630@googlegroups.com> <7b110d3e-ddb5-42a0-af99-aa5b0cb30832@googlegroups.com> <13efc313-d10c-4357-9aa7-6fa55b09d948@googlegroups.com> <87po1xi2n1.fsf@bsb.me.uk> <87k1s5hror.fsf@bsb.me.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader02.eternal-september.org; posting-host="fd2ef88f3973fbdcdd5cf6f7f328cfd4"; logging-data="5338"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+oD5f7AgJDS2YRVgrwfiyF" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:ZEtGsJe+BP7LICziC1dCixCqC1I= sha1:hCzHdDdK5ST6d2hhJ96XonWGRys= Xref: csiph.com comp.lang.c:130616 bartc writes: > On 15/05/2018 16:19, Ben Bacarisse wrote: >> bartc writes: >>> (My compiler tells me the first is 'unsigned char**' and the second is >>> 'unsigned char*'.) >> >> There is no "may" here -- they are of expressions of different types. >> The first type has type char (*)[4], not unsigned char **, and the >> second has type char *. I'm not sure where the unsigned comes from in >> your case. > > The special exception for & was not being applied to "...", as it is for > sizeof, so it just wrapped an extra pointer level around "...". > > The unsigned char is because I deliberately don't support plain char; it > must be either signed or unsigned rather than unspecified, and I chose > to make it unsigned. Please make it clear when you're talking about a language than C. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"