Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Adam Fedor <fedor@doc.com>
To: gdb-patches@sources.redhat.com
Cc: Andrew Cagney <ac131313@redhat.com>, Klee Dienes <klee@mit.edu>
Subject: Re: Add rules for ObjC files
Date: Thu, 24 Oct 2002 20:33:00 -0000	[thread overview]
Message-ID: <3DB6D629.50808@doc.com> (raw)
In-Reply-To: <3DB4826D.8050606@doc.com>

  Andrew Cagney wrote:

>> Klee Dienes wrote:
>> ObjC is supposed to be a strict superset of C, so at least in theory,
>> extensions don't need to be conditionalized at all, or they can be
>> disallowed after parsing, if you wanted to have a "strict C mode"
>> (although I note that the little array@45 extension is always available,
>> even though it's not valid C).
>
>
>
> (time passes)
>
> (array@45 is documented as a GDB CLI extension).
>
> Keeping the objective C .y separate from the C .y, I think, is a 
> better long term strategy.  While it will mean that someone needs to 
> keep the two files in sync, it also means that the objective C, C and 
> C++ parsers are guarenteed to not stomp on each others toes.
>

Well since the parsers probably aren't going to be combined yet :-) I'll 
un-withdraw this patch. Can someone approve it?

-- 
Adam Fedor, Digital Optics Corp.      | I'm glad I hate spinach, because
http://www.doc.com                    | if I didn't, I'd eat it, and you
                                       | know how I hate the stuff.



      reply	other threads:[~2002-10-25  3:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03 18:53 Adam Fedor
2002-10-04  2:25 ` Klee Dienes
2002-10-04  9:07   ` Adam Fedor
2002-10-04  9:49   ` Stan Shebs
2002-10-04 13:20     ` Klee Dienes
2002-10-04 14:49       ` Michael Snyder
2002-10-04 15:31         ` Kevin Buettner
2002-10-21 12:08   ` Andrew Cagney
2002-10-21 15:40     ` Adam Fedor
2002-10-24 20:33       ` Adam Fedor [this message]

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=3DB6D629.50808@doc.com \
    --to=fedor@doc.com \
    --cc=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=klee@mit.edu \
    /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