Re: Forth, TCL, Telescript

Billy Tanksley <tanksley@fallbrook.csusm.edu>

Mail folder: 1Q1994 Zoomer-List Archives
Next message: Jack Miller: "Re: Palm file format info "
Previous message: Brian Smithson: "World Clock bug"
In-reply-to: John D. Mitchell: "Forth, TCL, Telescript"
Reply: Doug Sewell: "Re: Forth, TCL, Telescript"

Errors-To: brian@grot.starconn.com
Date: Fri, 28 Jan 94 16:22 PST
Message-id: <Pine.3.05a.9401281106.C12318-b100000@fallbrook.csusm.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: Billy Tanksley <tanksley@fallbrook.csusm.edu>
To: Multiple recipients of list <zoomer-list@grot.starconn.com>
Subject: Re: Forth, TCL, Telescript
Status: OR

On Fri, 28 Jan 1994, John D. Mitchell wrote:

> Re: Forth
> 	Perhaps, but coming up with a nice visual way to deal with the text
> oriented language would seem to be quite difficult.  Also, Forth folks seem
> hell bent on never standardizing on what the language (and it's library)
> really is.  Forthers also just love to program the bare metal and seem to
> have problems with giving up total control to anyone/anything else (like
> the kernel).  Just my warped view of course. :-)

I will make the editor (which will be the whole forth) smart-- it will be
able to 1) built-in buttons (just type the text that will appear on the
button, accept default placement) and 2) externally designed buttons and
layouts.  I'm not sure how I will implement the last-- if someone would
write a layout tool that outputs in simple form, I could use that.

> Re: Telescript
> 	Who knows?  It would seem to depend greatly on what the scope of
> the capabilities of the language are.  Beats me.

It's an interpreted language that is designed to be very safe.  Because of
this, you can send these programs over a net and the computer at the other
side can run them without worrying about safety.

> Re: Tcl
> 	The only big problem with Tcl is that it passes nearly everything
> around as (sometimes huge) strings.  It's pretty easy to end up blowing out
> a 64Kb offset size that way.  This is my biggest reason for wanting a
> 32-bit offset version of GEOS (e.g., protected mode).

Would be wonderful.  :)

> Oh well, just my ramblings,
> 			John

Hey, same here.

By the way, could you give me some info on the Geos file format?  And any
details on Geos assembly?  The SDK docs are miserable on those.

-Billy
GeoHacker