From owner-freebsd-current Sun Nov 1 07:18:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19644 for freebsd-current-outgoing; Sun, 1 Nov 1998 07:18:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomad.dataplex.net (nomad.dataplex.net [208.2.87.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19638 for ; Sun, 1 Nov 1998 07:18:48 -0800 (PST) (envelope-from rkw@nomad.dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.1/8.9.1) with ESMTP id JAA17201; Sun, 1 Nov 1998 09:18:28 -0600 (CST) (envelope-from rkw@nomad.dataplex.net) Date: Sun, 1 Nov 1998 09:18:28 -0600 (CST) From: User RKW To: "Jordan K. Hubbard" cc: Mike Smith , Andrzej Bialecki , current@FreeBSD.ORG Subject: Re: BootForth (was Re: New boot loader and alternate kernels) In-Reply-To: <18893.909930119@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 1 Nov 1998, Jordan K. Hubbard wrote: > > So, how do I integrate it into the loader? Do we want to make it > > optional? Do we want to strip the loader back to the bare essentials > > and use BootFORTH for as much as possible? Is a "middle road" approach > > preferred? > > Well, you could probably save some space by registering all your existing > builtins as forth words and chucking the existing interpreter in favor > of the more traditional INTERPRET word. Not sure how you'd do that initial > timeout behavior thing though - probably some gross hack. :-) To make it small, that is the approach I would follow. Mixing languages leads to "bloat" because you end up supporting multiple ways to accomplish the same thing. KISS. As for the timeout, run a "word" that delays until its counter runs out or it finds a key. When that routine returns, test ?KEY to either read the actual input or fake it in the case of a timeout. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message