Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: uweigand@de.ibm.com, gdb-patches@sourceware.org
Subject: Re: [RFC/RFA] Introduce new struct parse_context
Date: Mon, 17 Dec 2007 20:35:00 -0000	[thread overview]
Message-ID: <uhcihjdbo.fsf@gnu.org> (raw)
In-Reply-To: <20071217064213.GC9022@adacore.com> (message from Joel Brobecker 	on Mon, 17 Dec 2007 10:42:13 +0400)

> Date: Mon, 17 Dec 2007 10:42:13 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> 
> I would like to introduce a new structure called "struct parse_context"
> which, for now, would contain the language and radix to use when doing
> some parsing. This is something that we already discussed in a more
> general way.

Thanks!

> This patch introduces:
> 
>   - struct parse_context
> 
>   - A function called "build_parse_context" that builds a parse_context
>     structure from a language and radix. Eventually, when the struct
>     grows, we will add more parameters to that function.
> 
>   - A macro: current_parse_context which returns a parse context using
>     the current_language and the input_radix.  This is the context that
>     we should be using when parsing from a function that is a "command"
>     (that is a function that implements a command)
> 
>   - A macro: wrong_parse_context, which is an alias to current_parse_context.
>     This macro is useful to help breaking this task into incremental changes
>     and is temporary, as the FIXME explains. I am using this macro when
>     I am in a context where I don't have the parse_context to be used (yet),
>     to make sure that I don't forget to fix it later. Will be removed
>     when the task is complete.

How about if we try to document in gdbint.texinfo each new
infrastructure we introduce, from now on?  Would other maintainers
support such a requirement from contributors?  I can offer
text-to-Texinfo conversion services (and, of course, general help in
writing documentation), if someone does not feel up to speed with
Texinfo.

WDYT?


  parent reply	other threads:[~2007-12-17 20:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17  7:03 Joel Brobecker
2007-12-17 13:34 ` Daniel Jacobowitz
2007-12-17 20:35 ` Eli Zaretskii [this message]
2007-12-21  5:02   ` Joel Brobecker
2007-12-21 16:34     ` Eli Zaretskii
2007-12-22  6:27       ` Joel Brobecker
2007-12-22 17:39         ` Eli Zaretskii
2007-12-26 11:04           ` Joel Brobecker
2007-12-29 22:44             ` Eli Zaretskii

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=uhcihjdbo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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