From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24978 invoked by alias); 26 Sep 2002 21:09:53 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 24971 invoked from network); 26 Sep 2002 21:09:53 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 26 Sep 2002 21:09:53 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 17ugpN-000781-00; Thu, 26 Sep 2002 17:09:45 -0500 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 17ufte-0001E2-00; Thu, 26 Sep 2002 17:10:06 -0400 Date: Thu, 26 Sep 2002 14:09:00 -0000 From: Daniel Jacobowitz To: Jim Blandy Cc: gdb@sources.redhat.com, fnasser@redhat.com Subject: Re: RFC: Additional testsuite alternative Message-ID: <20020926211006.GB4533@nevyn.them.org> Mail-Followup-To: Jim Blandy , gdb@sources.redhat.com, fnasser@redhat.com References: <20020916192546.GA6174@nevyn.them.org> <20020926182132.GA26853@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i X-SW-Source: 2002-09/txt/msg00459.txt.bz2 On Thu, Sep 26, 2002 at 03:50:07PM -0500, Jim Blandy wrote: > > 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. Now that's the kind of suggestion I was really fishing for. I'll investigate further - I like it. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer