Path: csiph.com!news.swapon.de!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: New "Forth" MCU Board, ChipStick Date: Thu, 31 Mar 2016 23:23:32 -0700 Organization: A noiseless patient Spider Lines: 14 Message-ID: <87fuv5sv8b.fsf@nightsong.com> References: <5ffa7735-547a-4352-b5d7-935656f3471a@googlegroups.com> <87oa9urseo.fsf@nightsong.com> <9d7cf792-fdb4-4f98-bf22-96279aa29e16@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="ac130717aa033f117b1251f50cb4c61b"; logging-data="2541"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+QoKKGdnPGAlOSAPqPdYEF" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:l2iHftQTQue0zvWdQRnQXY21h5Q= sha1:9zvTf5WfEON9PZWlejQgAvqdJlA= Xref: csiph.com comp.lang.forth:46381 visualforth@rocketmail.com writes: > Look at Jupiter ACE user manual Chapter 7, Altering word definitions: > How to correct mistakes, using LIST, EDIT and REDEFINE. Heh, I like that manual. But that doesn't look easier than a block editor to implement or use. Is it a colorforth-like tokenizing system? I can see how that can save some space, but I think it's better to store source code as text, so that formatting and comments are preserved. It's interesting that they enlarged the amount of sram from 2k (in the older fram parts) to 4k in this current one. I guess people didn't want to use fram as sram as much of the time as TI expected. Either way it seems like plenty for stacks and the more important user and system code and variables.