From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16008 invoked by alias); 9 Aug 2002 21:16:03 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 15981 invoked by uid 71); 9 Aug 2002 21:16:02 -0000 Date: Fri, 09 Aug 2002 14:51:00 -0000 Message-ID: <20020809211602.15980.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Nicolas Noble Subject: Re: c++/7562: strange behaviour with typedef and consts Reply-To: Nicolas Noble X-SW-Source: 2002-08/txt/msg00203.txt.bz2 List-Id: The following reply was made to PR c++/7562; it has been noted by GNATS. From: Nicolas Noble To: Geoff Keating Cc: Nicolas Noble , Subject: Re: c++/7562: strange behaviour with typedef and consts Date: Fri, 9 Aug 2002 23:15:16 +0200 (CEST) > Nicolas Noble writes: > > > typedef void * voidp; > > > > void func1(const voidp p) { } > > > > void func2(const void * p) { > > func1(p); > > } > > 'const voidp p' is the same as 'void * const p', not 'const void * p'. > It is correct for the compiler to complain here. Yeah, I understand perfectly... even if said like that it *IS* clear, I was confused by the zlib.h header. I'll complain to Jean-Loup Gailly then to correct his code :-) Thanks a lot! -- Nicolas Noble