Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Paul Hilfinger <hilfingr@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add language-dependent post-parser
Date: Fri, 09 Apr 2004 22:40:00 -0000	[thread overview]
Message-ID: <20040409214221.GA851@nevyn.them.org> (raw)
In-Reply-To: <20040407093235.B3165F2D8C@nile.gnat.com>

On Wed, Apr 07, 2004 at 05:32:35AM -0400, Paul Hilfinger wrote:
> 
> Here is a second version of the post-parser patch I submitted before.
> The Ada module will use the post-parser to do static overloaded name
> resolution at translation time.  The patch gives the current languages
> a default nop post-parser.
> 
> I think I have addresses Daniel's comments.  In this revision, I have
> simplified the interface to the post-parser and to
> parse_expression_in_context so that instead of an expected type, they
> just take a flag indicating whether the client expects a value (as
> opposed to simply evaluating for side effects).  
> 
> At the moment, nothing uses this flag in the public sources.  In ACT's
> code (in a change I will propose later), we have modified the 'call'
> command to use this flag, and our post-parser uses the void/non-void
> context distinction to disambiguate between overloaded procedures
> (void-returning functions) and value-returning functions.  This sort
> of limited, context-dependent disambiguation is not useful in C or
> C++, but is useful in Ada.  We do not implement Ada's full
> context-dependent type resolution; for the debugger, that simply turns
> out to be overkill.
> 
> This better?

Thanks; this is OK.

> 2004-03-04  Paul N. Hilfinger  <Hilfinger@gnat.com>
> 
> 	* language.h (language_defn): Add new la_post_parser field.
> 	* parser-defs.h (null_post_parser): New declaration (default for
> 	la_post_parser).
> 	
> 	* parse.c (parse_exp_1): Move code to parse_exp_in_context and
> 	insert call to that function.
> 	(parse_exp_in_context): New function, including code formerly in
> 	parse_exp_1.  Calls language-dependent post-parser after 
> 	prefixification.
> 	(parse_expression_in_context): New exported function.
> 	(null_post_parser): New definition.
> 	* expression.h (parse_expression_in_context): Add declaration.
> 	
> 	* p-lang.c (pascal_language_defn): Add trivial post-parser.
> 	* c-lang.c (c_language_defn): Ditto.
> 	(cplus_language_defn): Ditto.
> 	(asm_language_defn): Ditto.
> 	(minimal_language_defn): Ditto.
> 	* f-lang.c (f_language_defn): Ditto.
> 	* jv-lang.c (java_language_defn): Ditto.
> 	* language.c (unknown_language_defn): Ditto.
> 	(auto_language_defn): Ditto.
> 	(local_language_defn): Ditto.
> 	* m2-lang.c (m2_language_defn): Ditto.
> 	* scm-lang.c (scm_language_defn): Ditto.
> 	* obj-lang.c (objc_language_defn): Ditto.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-04-09 22:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19  0:09 Paul Hilfinger
2004-03-04 11:33 ` Paul Hilfinger
2004-03-19  0:09 ` Daniel Jacobowitz
2004-03-04 22:29   ` Daniel Jacobowitz
2004-03-05  8:15   ` Paul Hilfinger
2004-03-19  0:09     ` Paul Hilfinger
2004-04-02 16:33 ` Daniel Jacobowitz
2004-04-03 12:05   ` Paul Hilfinger
2004-04-07  9:32   ` Paul Hilfinger
2004-04-09 22:40     ` Daniel Jacobowitz [this message]
2004-04-10 22:12       ` Paul Hilfinger
2004-03-30  9:24 Paul Hilfinger
2004-03-30 14:27 ` Daniel Jacobowitz
2004-03-31  8:02   ` Paul Hilfinger
2004-03-31 15:30     ` Daniel Jacobowitz
2004-03-31 15:36       ` Daniel Jacobowitz
2004-03-31 16:49         ` Andrew Cagney
2004-03-31 16:58           ` Daniel Jacobowitz
2004-04-01 10:43             ` Paul Hilfinger
2004-04-02 16:25               ` Andrew Cagney

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=20040409214221.GA851@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=hilfingr@gnat.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