Forth, TCL, Telescript

"John D. Mitchell" <johnm@cory.EECS.Berkeley.EDU>

Mail folder: 1Q1994 Zoomer-List Archives
Next message: Billy Tanksley: "Re: Forth, TCL, Telescript"
Previous message: Billy Tanksley: "Re: Forth, TCL, Telescript"
In-reply-to: Billy Tanksley: "Re: Forth, TCL, Telescript"
Reply: Billy Tanksley: "Re: Forth, TCL, Telescript"

Errors-To: brian@grot.starconn.com
Date: Tue, 1 Feb 94 16:12 PST
Message-id: <199402012255.OAA10825@cory.EECS.Berkeley.EDU>
X-Comment: Zoomer PDA List
Originator: zoomer-list@grot.starconn.com
Errors-To: brian@grot.starconn.com
Reply-To: <zoomer-list@grot.starconn.com>
Sender: zoomer-list@grot.starconn.com
X-Listserv-Version: 5.5 -- Copyright (c) 1991/92, Anastasios Kotsikonas
From: "John D. Mitchell" <johnm@cory.EECS.Berkeley.EDU>
To: Multiple recipients of list <zoomer-list@grot.starconn.com>
Subject: Forth, TCL, Telescript
Status: OR

Re: "Linking in their own structure"
>Sorry, that was vague.  By 'structure', I mean the stucture of the user
>interface-- the buttons, menus, and arrangement thereof.

Hmm..., are you talking about letting them write 'code' external to your
program that you read in as "source" or 'link in' as in a linker or
something else?

Re:  Tcl
>How could I make my Forth compatible with some future implementation of
>Tcl?

I'm not sure what you mean.  Tcl is a language in its own right.  In that
sense, I'll throw my $0.02 into the pot and say that I'd much rather see a
port/implementation of Tcl to GEOS than Forth. :-)  I guess you could make
your Forth implementation 'compatible' with Tcl by just embedding a Tcl
interpreter in your Forth system.  :-)

John