Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Matt Rice <ratmice@gmail.com>
To: Doug Evans <dje@google.com>
Cc: Keith Seitz <keiths@redhat.com>,
	gdb-patches@sourceware.org, 	Pedro Alves <pedro@codesourcery.com>,
	Tom Tromey <tromey@redhat.com>
Subject: Re: [RFA] c++/11734
Date: Thu, 24 Jun 2010 11:39:00 -0000	[thread overview]
Message-ID: <AANLkTilhJAy0k_-SWLOdSrR42oUs2E-9av5-DhO-ELVY@mail.gmail.com> (raw)
In-Reply-To: <AANLkTil8J9g3Z3mJn0Tcw225FAlU-e1CNKmFblwb9hmt@mail.gmail.com>

On Wed, Jun 23, 2010 at 7:25 PM, Doug Evans <dje@google.com> wrote:

> "c::foo" looks enough like an objc symbol that decode_objc will call
> lookup_symbol ("c::foo")

its possibly worth noting that c::foo is not really a valid
objective-c selector/method name

a method which would contain unnamed message pieces (not really sure
the correct wording)
which would lead to '::' also must end in a colon.

so the following method is valid:

- (int) c:(int)a :(int)b foo:(int)c;
{
  return a + b + c;
}

which would equal 'c::foo:'

while 'foo' is a valid for a name for a method which has no parameters
and does not end in a colon.
you can't mix and match parameter taking message pieces and
non-paramater accepting ones in the same message,
they either do or they don't accept parameters.

and making it foo:(void) isn't valid either.


  reply	other threads:[~2010-06-24 11:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22  1:22 Keith Seitz
2010-06-22  9:45 ` Pedro Alves
2010-06-22 15:43   ` Keith Seitz
2010-06-23 17:33     ` Keith Seitz
2010-06-24  2:25     ` Doug Evans
2010-06-24 11:39       ` Matt Rice [this message]
2010-06-24 16:05       ` Doug Evans
2010-06-24 20:01       ` Tom Tromey
2010-06-24 20:49         ` Doug Evans
2010-06-24 20:51       ` Keith Seitz

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=AANLkTilhJAy0k_-SWLOdSrR42oUs2E-9av5-DhO-ELVY@mail.gmail.com \
    --to=ratmice@gmail.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.com \
    --cc=pedro@codesourcery.com \
    --cc=tromey@redhat.com \
    /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