public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Geoff Keating <geoffk@geoffk.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7562: strange behaviour with typedef and consts
Date: Fri, 09 Aug 2002 14:16:00 -0000 [thread overview]
Message-ID: <20020809211601.15961.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/7562; it has been noted by GNATS.
From: Geoff Keating <geoffk@geoffk.org>
To: Nicolas Noble <nicolas@nobis-crew.org>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/7562: strange behaviour with typedef and consts
Date: 09 Aug 2002 14:12:42 -0700
Nicolas Noble <nicolas@nobis-crew.org> 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.
--
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>
next reply other threads:[~2002-08-09 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 14:16 Geoff Keating [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-09 14:51 Nicolas Noble
2002-08-09 14:16 Graham Stott
2002-08-09 14:06 Nicolas Noble
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020809211601.15961.qmail@sources.redhat.com \
--to=geoffk@geoffk.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).