delorie.com/archives/browse.cgi | search |
From: | jdashiel AT eagle1 DOT eaglenet DOT com |
Date: | Thu, 13 Feb 1997 20:37:20 -0500 (EST) |
To: | mharris AT blackwidow DOT saultc DOT on DOT ca |
Cc: | OpenDOS <opendos AT mail DOT tacoma DOT net> |
Subject: | Re: [opendos] [OpenDOS] All of them nice ideas |
In-Reply-To: | <Pine.LNX.3.95.970213052306.118C-100000@capslock.com> |
Message-Id: | <Pine.NXT.3.95.970213203055.1191H-100000@eagle1> |
Mime-Version: | 1.0 |
Sender: | owner-opendos AT mail DOT tacoma DOT net |
I'm proposing that that possibility be considered. Normally when programs are compiled in forth it's possible to strip the kernel of forth used in that compilation down to only commands used by that program. That's possible in tcom in f-pc however the slow word isn't implemented in f-pc so newui=off interface wouldn't be possible until that omission is ammended. It may end up that code bloat experienced in m$dog might be removed were forth used. I wouldn't even try compilation of sources in forth without reading Gear's Forth The Next Step though if for no other reason than learning good documentation standards for forth programming though. That book was written for forth79 but information and code transports to other forth systems rather easily. jude <jdashiel AT eagle1 DOT eaglenet DOT com>
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |