Path: csiph.com!usenet.pasdenom.info!aioe.org!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: blocks and screens, tell your war stories Date: Thu, 15 Jan 2015 23:08:03 -0800 Organization: A noiseless patient Spider Lines: 19 Message-ID: <87zj9jmcdo.fsf@jester.gateway.pace.com> References: <878uhdum3e.fsf@jester.gateway.sonic.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="cf2250d04a15656821738afa87e3379c"; logging-data="3072"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19blrgdZxRN3wj3gQfKhDTk" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:+ZhL7hIjoF3dz+Qb+R5E/A5GVBo= sha1:4LahxVu/jo8ua//pH/WQU/JUa7Y= Xref: csiph.com comp.lang.forth:35840 rickman writes: > I haven't looked at this entire thread to see if the GA development > system is discussed much. Has anyone taken a look at that? I know it > uses blocks and screens. When I tried to see how to use it they > seemed to have a very intricate system with multiple levels/layers > that, frankly, was beyond me on the first pass. It was one of the > most convoluted things I have seen. I've looked at it but not tried it. It was one of the inspirations for my posting this thread. I assume its use of blocks is traditional. The separation of edit time from compile time (i.e. with significant processing done at edit time) seems to come from colorforth. The whole thing has an interesting steampunk feel, it seems to me. Why on earth does anyone with a modern PC tokenize the input at edit time in order to save at most a few milliseconds on compilation? I do miss Jeff Fox who may have originated that scheme, in his Aha system. And I just don't understand how anyone could get anything done in colorforth, much less write something like OKAD.