Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: GDB Focus Group at the 2008 GCC Summit
Date: Mon, 23 Jun 2008 15:16:00 -0000	[thread overview]
Message-ID: <m3mylc18tn.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20080619190942.GA3744@adacore.com> (Joel Brobecker's message of "Thu\, 19 Jun 2008 15\:09\:42 -0400")

>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

Joel> | * Calling python function from the CLI:
Joel> |     Several possible syntaxes:
Joel> |       $(function-name arguments)
Joel> |       $function_name (arguments)
Joel> |     And also, should be treat the arguments as a simple string,
Joel> |     or should we treat each argument as an expression?
Joel> |     We reached a consensus and Tom to send it to the gdb list.

Our consensus was to use the function-like syntax (second example
above) and to parse the arguments as expressions.  This does mean
there is a namespace issue, but we reasoned that we could make all the
standard functions have a "gdb_" prefix or something like that.

I'm about 80% done with implementing this.  I'm using an approach
suggested by Daniel, which is to add a new "convenience function"
type.

Also we agreed that new Python classes should use implicit Python
functions when it makes sense -- that is, use __str__ rather than an
explicit to_string.

Tom


  parent reply	other threads:[~2008-06-23 15:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 19:10 Joel Brobecker
2008-06-22  6:08 ` Thiago Jung Bauermann
2008-06-22 11:52 ` Nick Roberts
2008-06-22 13:53   ` Joel Brobecker
2008-06-23 15:17   ` Tom Tromey
2008-06-23 17:35     ` Jim Ingham
2008-06-23 21:55     ` Nick Roberts
2008-06-23 15:16 ` Tom Tromey [this message]
2008-06-26  0:24   ` Tom Tromey
2008-07-03  3:27   ` Thiago Jung Bauermann
2008-07-03  8:12     ` Andreas Schwab
2008-07-03 12:35     ` Daniel Jacobowitz
2008-07-03 14:28       ` Thiago Jung Bauermann
2008-07-04  2:33       ` Tom Tromey
2008-07-04  3:19         ` Daniel Jacobowitz
2008-06-23 21:46 ` Jason Molenda
2008-06-23 22:22   ` Nick Roberts
2008-06-24 21:18     ` Nick Roberts
2008-06-25  6:56       ` [MI] changing breakpoint location (Was: GDB Focus Group at the 2008 GCC Summit) Vladimir Prus
2008-06-23 22:09 ` GDB Focus Group at the 2008 GCC Summit Mark Kettenis
2008-06-23 22:26   ` Joel Brobecker
2008-06-24  8:35   ` Andrew STUBBS
2008-06-24  8:56     ` Andreas Schwab
2008-06-24 18:12     ` Michael Snyder
2008-06-24 18:28     ` Daniel Jacobowitz
2008-06-24 19:33     ` Dave Korn

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=m3mylc18tn.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.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