Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paul Schlie <schlie@comcast.net>
To: Kip Macy <kmacy@fsmware.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: GDB/MI Output Syntax
Date: Thu, 06 Jan 2005 00:49:00 -0000	[thread overview]
Message-ID: <BE01F536.880E%schlie@comcast.net> (raw)
In-Reply-To: <20050105163128.U97844@demos.bsdclusters.com>

Well went back 2 years on the gdb list and found nothing indicating that it
was ever "decided against", but do acknowledge that it's academic unless
energy is committed to it or any other implementation.

> From: Kip Macy <kmacy@fsmware.com>
> Similar alternatives have been discussed previously and decided against.
> Check the archives for details.
> 
> -Kip
> 
>> Or how about a basic scheme (<keyword> <expression> ...) syntax, can't get
>> much simpler or more flexible than that, not to mention it's fairly straight
>> forward easy to read/parse/extend and may realativly easily accomplished by
>> imbedding an open-source basic scheme interpreter, vs re-inventing the
>> wheel; nearly eliminating the necessity for steps 1, 2; and longer term
>> could easily eliminate gdb's present less than flexible command interpreter,
>> as there's truly no good reason for the two to be distinct. (Not a new
>> notion; but possibly timely and arguably far more productive than developing
>> yet another yet another syntax/language/intepreter/etc.)



  reply	other threads:[~2005-01-06  0:49 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06  0:28 Paul Schlie
2005-01-06  0:32 ` Kip Macy
2005-01-06  0:49   ` Paul Schlie [this message]
2005-01-06  1:10 ` Bob Rossi
2005-01-06  1:36   ` Paul Schlie
     [not found] <1093622671.2836.ezmlm@sources.redhat.com>
2004-08-27 17:56 ` Jim Ingham
2004-08-27 19:12   ` Michael Chastain
2005-01-05 23:27     ` Bob Rossi
2005-01-06  4:48       ` Eli Zaretskii
2005-01-06 23:31         ` Bob Rossi
2005-01-07  0:36           ` Jim Ingham
2005-01-07  1:12             ` Bob Rossi
2005-01-07  3:12               ` Russell Shaw
2005-01-11 19:35                 ` Bob Rossi
2005-01-13  2:23                   ` Bob Rossi
  -- strict thread matches above, loose matches on Subject: below --
2004-08-25 15:44 Bob Rossi
2004-08-25 15:57 ` Michael Chastain
2004-08-25 19:37   ` Bob Rossi
2004-08-26 14:01     ` Michael Chastain
2004-08-26 18:31       ` Bob Rossi
2004-08-26 20:44         ` Michael Chastain
2004-08-26 20:52           ` Keith Seitz
2004-08-26 22:16             ` Michael Chastain
2004-08-26 22:03           ` Bob Rossi
2004-08-26 23:06             ` Michael Chastain
2004-08-26 21:13 ` Andrew Cagney
2004-08-26 21:25   ` Bob Rossi
2004-08-26 22:46     ` Michael Chastain
2004-08-27 10:14       ` Eli Zaretskii
2004-08-26 22:41   ` Michael Chastain
2004-08-24  3:12 Bob Rossi
2004-08-24  4:15 ` Michael Chastain
2004-08-24 12:30   ` Bob Rossi
2004-08-24 12:50     ` Michael Chastain
2004-08-24 18:59   ` Andrew Cagney
2004-08-24 19:07     ` Bob Rossi

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=BE01F536.880E%schlie@comcast.net \
    --to=schlie@comcast.net \
    --cc=gdb@sources.redhat.com \
    --cc=kmacy@fsmware.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