From: John Fine <johnsfine@verizon.net>
To: Rodolfo Lima <rodolfo@rodsoft.org>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Errors using the same identifier as type and function name
Date: Tue, 02 Sep 2008 01:00:00 -0000 [thread overview]
Message-ID: <48BC8FDD.3040001@verizon.net> (raw)
In-Reply-To: <g9hvic$9df$1@ger.gmane.org>
Rodolfo Lima wrote:
> the fact that we're referencing 'struct type' *before* specifying
> 'A::type' function name shouldn't make both identifiers ambiguous.
>
>
Sequence doesn't work that way when declaring members. Inside a struct
definition, you can use a member name before declaring it.
next prev parent reply other threads:[~2008-09-02 1:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 23:59 Rodolfo Lima
2008-09-02 1:00 ` John Fine [this message]
2008-09-02 1:12 ` Rodolfo Lima
2008-09-02 12:11 ` Marco Manfredini
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=48BC8FDD.3040001@verizon.net \
--to=johnsfine@verizon.net \
--cc=gcc-help@gcc.gnu.org \
--cc=rodolfo@rodsoft.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).