Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!fu-berlin.de!uni-berlin.de!not-for-mail From: David Kuehling Newsgroups: comp.lang.forth Subject: Re: Gforth-EC, the underappreciated embedded Forth Date: Tue, 07 Feb 2012 16:55:56 +0100 Lines: 36 Message-ID: <8762fibptf.fsf@mosquito.pool> References: <87fwen62fr.fsf@snail.Pool> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: news.uni-berlin.de T4E+T6o31eLLZ/y+6pRrlQsKwODNqVoubRVCez0r1I5vGztbY= Cancel-Lock: sha1:E9O+zGb3bw8NGKSeBjJyQWP0hEE= User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) Xref: x330-a1.tempe.blueboxinc.net comp.lang.forth:9431 >>>>> "Albert" == Albert van der Horst writes: > In article <87fwen62fr.fsf@snail.Pool>, > David Kuehling wrote: >> Hi, >> >> I've been having a look at Gforth-EC lately, that's the embedded >> cross-compiled Forth support that has been included with Gforth all >> the time, but as it's well hidden and pretty undocumented, I guess >> most people wouldn't have noticed it. >> >> Now it turns out it only takes a few commands to generate a usable >> 8086 gforth-ec executable, running in dosbox (i.e. emulated under >> Linux): >> >> From the Gforth source directory, run: >> >> ./build-ec 8086 mv kernl-8086.fi gforthec.com # need to rename for >> dosbox to execute it dosbox gforthec.com > Slightly surprising. I expect a Forth only to run on a dosbox if it > does INT 21 io. I expect an embedded Forth to work independant from > MSDOS INT 21 stuff. It does use int 21 io, see definition of (emit) &friends in [1]. The nice thing is that this is really completely compiled&assembled from forth. No binutils, GCC etc. involved. cheers, David [1] http://www.complang.tuwien.ac.at/cvsweb/cgi-bin/cvsweb/gforth/arch/8086/prim.fs?rev=1.6;content-type=text%2Fplain -- GnuPG public key: http://dvdkhlng.users.sourceforge.net/dk.gpg Fingerprint: B17A DC95 D293 657B 4205 D016 7DEF 5323 C174 7D40