Path: csiph.com!news.swapon.de!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: blocks and overlays question Date: Tue, 27 Sep 2016 11:22:18 -0700 Organization: A noiseless patient Spider Lines: 13 Message-ID: <87inth5hk5.fsf@jester.gateway.pace.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="2aed369a7b4699bde3e169ff4d831123"; logging-data="29661"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18D0b2TQzDEq2Zp6dG71zr4" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:xGX9IkScYsvH0NhI8zqcqrUQHZo= sha1:xGYUYMa5jHq6Ro9CA3cwHnWLVAQ= Xref: csiph.com comp.lang.forth:51394 Can anyone say how overlays traditionally worked in Forth? E.g. you'd load some program fragment with block loads, but then how would you get rid of it when you were done? With FORGET directly? How much storage did it take for a block system to make any sense? Any idea how much disk space (and ram) F83 used? Motivation of question: wondering about the idea of an F83-like environment inside an MCU, like one of the cheap Cortex parts with 20k of ram and 64k or 128k of program flash, using some of the flash as block storage. Example: https://www.aliexpress.com/item//32369020878.html