From owner-freebsd-config Wed Apr 30 04:45:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA22526 for config-outgoing; Wed, 30 Apr 1997 04:45:35 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA22520 for ; Wed, 30 Apr 1997 04:45:32 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id VAA28537; Wed, 30 Apr 1997 21:08:54 +0930 (CST) From: Michael Smith Message-Id: <199704301138.VAA28537@genesis.atrad.adelaide.edu.au> Subject: Re: Startup userconfig parsing In-Reply-To: <26868.862397611@time.cdrom.com> from "Jordan K. Hubbard" at "Apr 30, 97 03:53:31 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 30 Apr 1997 21:08:53 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, bde@zeta.org.au, config@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-config@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > Yes, that it most unfortunately does. :( Last time Poul-Henning was > making semi-serious noises about this, I looked into it quickly and > then looked away again just as quickly. The entire file I/O system > would need to be hacked off with a knife and reimplimented in a much > more kernel-centric context, for one thing, and we don't even want to > talk about the process control. :) I went back to about Tcl 3 or 4, and even back then it was Way Too Big. > The problem likes not with forth, but with its available public > implementations: They all suck, in one crucial way or another. :-( I was afraid of that. 8( > them off for right now, despite some compelling speed advantages (but > hey - this ain't for racing, right? It's for getting to the race > track :-). Yup. Specifically, it's meant to provide a parser, and some simple from-userspace kernel scripting. > And finally, the one I was actually playing with recently, is > "atlast" Atlast (by John Walker of AutoCAD fame) is actually > very small, very easy to embed into C (in fact, that was its > purpose) and very easy to add new words (in C) to. All desirable attributes. n fact, in the first draft of the message I sent you, I had attached the first few paragraphs from the ATLAST README 8) I was also looking at the 'diesel' interpreter he did, which would probably be more Bruce's style 8) > I finally gave up on atlast as not a "real enough" implementation of > forth for a complete sysinstall type solution, but perhaps it's enough > for bootstrap purposes. It would need to be pruned somewhat, but it's certainly an option worth considering. > Otherwise, we could ask Mitch for his forth. I think that'd > be the best "full forth" solution, if we even want to go that > route. What sort of size are we talking about? > Jordan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[