Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #51411
| Path | csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail |
|---|---|
| From | Paul Rubin <no.email@nospam.invalid> |
| Newsgroups | comp.lang.forth |
| Subject | Re: blocks and overlays question |
| Date | Tue, 27 Sep 2016 16:54:53 -0700 |
| Organization | A noiseless patient Spider |
| Lines | 16 |
| Message-ID | <87shsk525u.fsf@jester.gateway.pace.com> (permalink) |
| References | <87inth5hk5.fsf@jester.gateway.pace.com> <nsef3p$4rt$1@cherry.spenarnc.xs4all.nl> <87eg455e41.fsf@jester.gateway.pace.com> <E7idnQTh5-cHTnfKnZ2dnUU7-b3NnZ2d@supernews.com> <8760ph5b3g.fsf@jester.gateway.pace.com> <VuWdnauvVPfCe3fKnZ2dnUU7-Q_NnZ2d@supernews.com> <87wphx3r8e.fsf@jester.gateway.pace.com> <Aq-dnWSsOYAvnHbKnZ2dnUU7-R_NnZ2d@supernews.com> |
| Mime-Version | 1.0 |
| Content-Type | text/plain |
| Injection-Info | mx02.eternal-september.org; posting-host="2aed369a7b4699bde3e169ff4d831123"; logging-data="32100"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX183LFu0y/KzQMO7GWLeqoK8" |
| User-Agent | Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) |
| Cancel-Lock | sha1:WuqA2J42Hz4/DDsQhYzh6gzuxzs= sha1:l/lod85w0elNdCsYC/GEBte+rT8= |
| Xref | csiph.com comp.lang.forth:51411 |
Show key headers only | View raw
"Elizabeth D. Rather" <erather@forth.com> writes: > Or, you can compile your common code to flash and run it there, and > use a little RAM for the overlays. That would require resetting the > dictionary pointer after the flash code is compiled, but shouldn't be > complicated. Maybe there will have to be two dictionaries, flash and ram. I'll check how FlashForth, Mecrisp, etc. deal with this. > During development, put your kernel and well-tested code in flash and > use RAM for testing. As the code becomes more stable, add it to the > flashed code. Sounds like a plan. Thanks for the help!
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