Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!news.swapon.de!fu-berlin.de!uni-berlin.de!news.dfncis.de!not-for-mail From: David Kuehling Newsgroups: comp.lang.forth Subject: Re: made it to page 4 of gforth tutorial Date: Fri, 22 Apr 2011 20:07:00 +0200 Lines: 23 Message-ID: <87aafikvnf.fsf@snail.Pool> References: <40897826-9ec5-42c7-bb7f-540e964cddac@z33g2000vbk.googlegroups.com> <99081415998436@frunobulax.edu> <7xbozz5u1n.fsf@ruckus.brouhaha.com> <7xoc3z9uuv.fsf@ruckus.brouhaha.com> <9sGdncwx26o0pyzQnZ2dnUVZ_hSdnZ2d@supernews.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: news.dfncis.de MYIWF5lNXKpPZpW7QqkF7AHQjWsYPAR4hzeND4MWQ+55W8 Cancel-Lock: sha1:i4B44wzUOuxDOWJPgvWf/z5TT/k= User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Xref: x330-a1.tempe.blueboxinc.net comp.lang.forth:1428 > Andrew Haley wrote: >> foxchip wrote: >>> > However iTV management wanted portable ANS code for the browser and >> email and the network protocols. It was done in ANS which required >> conventional stacks in external memory, and the stack pointers needed >> by certain ANS words. The ANS code did use about thirty stack cells >> in its apps. It also tended to be at least ten times larger and a >> hundred times slower than machineForth code. But management wanted a >> simple threaded ANS implementation rather than an optimizing native >> code compiler with the stacks in memory using stack pointers as >> required by ANS design. > What aspect of ANS actually requires stack pointers, though? The only > word I can think of is DEPTH, but I don't think it's very much used in > standard programs. There's certainly nothing in Standard Forth that > requires stacks to be in addressable memory. What about PICK and ROLL? David