Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: Memory Date: Sat, 28 Jan 2017 20:31:37 -0800 Organization: A noiseless patient Spider Lines: 25 Message-ID: <87d1f61o7q.fsf@nightsong.com> References: <87h94i20px.fsf@nightsong.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="d6a6d2a02c20d10462ae7f80899d3f26"; logging-data="26861"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/ii3y546s8Drge6ItKtf97" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:b+y54mhSTYPfviIRm3St5Jsx8Hc= sha1:vLd7fPF3rUbLLsSC5/7jx46tE5o= Xref: csiph.com comp.lang.forth:54512 Cecil Bayona writes: > eForth for the esp8266 is disappointing, eForth usually it's written > in assembler for the primitives but the esp8266 flavor is not, it's > written in C which is not the end of the world but on top of that it > is a token threaded Forth not know for it's speed instead it's used to > save on memory which the esp8266 has plenty of. A traditional ITC Forth would be relatively slow too compared with native code and subroutine threading. The esp8266 is fast compared to older MCUs and the even faster ESP32 is available now. In fact you can even run Python on the esp8266 (micropython.org). What are you doing that makes speed a worry? > It's not a total loss as it could be useful to quickly port eForth to > a FPGA CPU, or an oddball CPU. Is it the one below? It looks nice to me and I got it running on a PC without any trouble, iirc: http://chiselapp.com/user/tehologist/repository/compc/home > I'm having some issues with eForth as the tools used don't run under > Win10 64 bit OS, they were developed with Xp 32 bit version. What tools are those? I'm used to completely self-hosted eforths.