Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paul Koning <Paul_Koning@dell.com>
To: jimb@red-bean.com
Cc: dje@google.com,     tromey@redhat.com,     bauerman@br.ibm.com,
	    gdb@sourceware.org
Subject: Re: repo to work on python scripting support
Date: Thu, 27 Mar 2008 16:49:00 -0000	[thread overview]
Message-ID: <18411.48081.90160.97179@pkoning-laptop.equallogic.com> (raw)
In-Reply-To: <8f2776cb0803261544u6e4c9f60u9f3fbde4095e5ec8@mail.gmail.com>

>>>>> "Jim" == Jim Blandy <jimb@red-bean.com> writes:

 Jim> What kind of functions for parsing Python does the Python API
 Jim> export?  Is there anything that would, say, parse an expression
 Jim> as far as it can, and let us know where the expression ends?  If
 Jim> so, we could use that for $(py <python code here>), and things
 Jim> like embedded quotes and parens would just work.

I don't see anything to do this in http://docs.python.org/ext/ext.html
There are APIs to pass in the Python text, as a string, or as a file
-- but it appears that the text is expected to be valid Python code,
not Python code optionally followed by something else.

Lexically speaking Python is very simple; looking for the closing
paren in the proposed syntax wouldn't be a big deal.

      paul


  reply	other threads:[~2008-03-27 15:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-16  0:42 Thiago Jung Bauermann
2008-03-16  2:55 ` Tom Tromey
2008-03-24 17:16   ` Thiago Jung Bauermann
2008-03-25 11:45     ` Tom Tromey
2008-03-25 13:53       ` Daniel Jacobowitz
2008-03-25 18:37         ` Jim Blandy
2008-03-25 18:52           ` Daniel Jacobowitz
2008-03-25 18:53             ` Jim Blandy
2008-03-25 19:18             ` Tom Tromey
2008-03-27  6:41               ` Jim Blandy
2008-03-27 17:57                 ` Paul Koning
2008-03-25 19:31           ` Paul Koning
2008-03-25 20:18             ` Tom Tromey
2008-03-25 20:31               ` Paul Koning
2008-03-26  3:23                 ` Tom Tromey
2008-03-26 12:55                 ` Jim Blandy
2008-03-26 17:29                   ` Paul Koning
2008-03-26 17:58                     ` Daniel Jacobowitz
2008-03-26 18:41                     ` Tom Tromey
2008-03-26 20:04                       ` Paul Koning
2008-03-26 22:45                     ` Jim Blandy
2008-03-26 18:05       ` Doug Evans
2008-03-26 18:13         ` Daniel Jacobowitz
2008-03-26 18:25           ` Tom Tromey
2008-03-26 18:41             ` Daniel Jacobowitz
2008-03-26 18:55               ` Tom Tromey
2008-03-26 20:57                 ` Daniel Jacobowitz
2008-03-26 21:01                 ` Thiago Jung Bauermann
2008-03-27 14:11           ` Jim Blandy
2008-03-27 16:49             ` Paul Koning [this message]
2008-03-26 18:23         ` Tom Tromey

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=18411.48081.90160.97179@pkoning-laptop.equallogic.com \
    --to=paul_koning@dell.com \
    --cc=bauerman@br.ibm.com \
    --cc=dje@google.com \
    --cc=gdb@sourceware.org \
    --cc=jimb@red-bean.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