Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com, fnasser@redhat.com
Subject: Re: RFC: Additional testsuite alternative
Date: Thu, 26 Sep 2002 14:05:00 -0000	[thread overview]
Message-ID: <vt2k7l8cw74.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <20020926182132.GA26853@nevyn.them.org>


It's a pity to implement a little language in Tcl.  People always
introduce little languages, saying, "I just need a very simple
language for this one situation; I don't need anything complex."
And then, minor feature by minor feature, it grows, until you've got
the Bourne shell.

Doesn't the Tcl we're using nowadays have namespaces?  Can't we make
.x files just Tcl scripts that run in a namespace that has all the
right commands in it?  Then Daniel's example:

    #compile two.cc two.exe executable debug
    #runto main
    #test "ptype StrOne"
    type = class OneStruct {
      public:
        int simple;
    [synthetic OneStruct]}
    #test "ptype ConstStrOnePtr"
    type = const class OneStruct {
      public:
        int simple;
    [synthetic OneStruct]} \*

could just be:

    compile two.cc two.exe executable debug
    runto main
    test "ptype StrOne" {
    type = class OneStruct {
      public:
        int simple;
    [synthetic OneStruct]}
    }
    test "ptype ConstStrOnePtr" {
    type = const class OneStruct {
      public:
        int simple;
    [synthetic OneStruct]} \*
    }

And you've got all your quoting stuff, comments, substitution, etc for
free.  Designed carefully, not grown incrementally.


  parent reply	other threads:[~2002-09-26 21:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-16 12:25 Daniel Jacobowitz
2002-09-26 11:21 ` Daniel Jacobowitz
2002-09-26 12:51   ` David Carlton
2002-09-26 13:22   ` Fernando Nasser
2002-09-26 13:25     ` Daniel Jacobowitz
2002-09-26 14:05   ` Jim Blandy [this message]
2002-09-26 14:09     ` Daniel Jacobowitz
2002-09-26 13:47 ` Andrew Cagney
2002-09-26 13:57   ` Daniel Jacobowitz

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=vt2k7l8cw74.fsf@zenia.red-bean.com \
    --to=jimb@redhat.com \
    --cc=drow@mvista.com \
    --cc=fnasser@redhat.com \
    --cc=gdb@sources.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