Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #51402
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: blocks and overlays question |
| Date | 2016-09-27 13:25 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <87a8et5buu.fsf@jester.gateway.pace.com> (permalink) |
| References | <87inth5hk5.fsf@jester.gateway.pace.com> <de32ef92-68f6-42d9-9e9f-0530ad4fb881@googlegroups.com> |
foxaudioresearch@gmail.com writes: > On my old DOS HSF/Forth system, BLOCKS is a library you pull in. The > source code for just the blocks and buffers system is 154 lines of > code. It compiles to 1512 bytes without the names. It allows the > system to compile source code from blocks or files by vectoring the > appropriate words. Cool, thanks. But I'm realizing that loading blocks consumes ram and if it doesn't get released, it's better to compile the libraries into flash and run them from there. > My old TI-Forth system had floppy drives with only 90K byte per > disk. It worked great but slowly due to Fig-Forth and memory > wait-states on that !@#$! machine. Heh, I've always wondered what those environments were like. I've never tried booting Fig-Forth but F83 ran right away under a dos emulator. http://www.angelfire.com/in/zydenbos/WhatisForth.html claims: a self-contained interactive Forth system including an editor, assembler, and even multitasking support can easily be put in an 8 KB EPROM. I guess that meant Fig-Forth but even still, it's surprisingly small. > However some clever linking and unlinking of the dictionary > should have made a binary overlay to specific buffer possible. Cool, but I guess overlays are more trouble than they're worth in the imagined environment. Being able to compile code to flash and run it from there probably makes up for it.
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
blocks and overlays question Paul Rubin <no.email@nospam.invalid> - 2016-09-27 11:22 -0700
Re: blocks and overlays question albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2016-09-27 20:51 +0200
Re: blocks and overlays question Paul Rubin <no.email@nospam.invalid> - 2016-09-27 12:36 -0700
Re: blocks and overlays question "Elizabeth D. Rather" <erather@forth.com> - 2016-09-27 10:16 -1000
Re: blocks and overlays question Paul Rubin <no.email@nospam.invalid> - 2016-09-27 13:41 -0700
Re: blocks and overlays question "Elizabeth D. Rather" <erather@forth.com> - 2016-09-27 11:36 -1000
Re: blocks and overlays question Paul Rubin <no.email@nospam.invalid> - 2016-09-27 15:36 -0700
Re: blocks and overlays question "Elizabeth D. Rather" <erather@forth.com> - 2016-09-27 13:33 -1000
Re: blocks and overlays question Paul Rubin <no.email@nospam.invalid> - 2016-09-27 16:54 -0700
Re: blocks and overlays question albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2016-09-28 09:44 +0200
Re: blocks and overlays question hughaguilar96@gmail.com - 2016-09-27 12:22 -0700
Re: blocks and overlays question foxaudioresearch@gmail.com - 2016-09-27 12:51 -0700
Re: blocks and overlays question Paul Rubin <no.email@nospam.invalid> - 2016-09-27 13:25 -0700
Re: blocks and overlays question Mark Wills <markwills1970@gmail.com> - 2016-09-28 03:37 -0700
Re: blocks and overlays question foxaudioresearch@gmail.com - 2016-09-28 07:41 -0700
Re: blocks and overlays question Mark Wills <markwills1970@gmail.com> - 2016-09-28 15:05 -0700
csiph-web