Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #28787
| From | stephenXXX@mpeforth.com (Stephen Pelc) |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: RfD: Interpret S\" |
| Organization | MPE |
| Message-ID | <530e053e.94589271@news.demon.co.uk> (permalink) |
| References | <op.xbtceeqosu5d0p@david> <530c6015.1058201878@news.demon.co.uk> <2014Feb26.120034@mips.complang.tuwien.ac.at> |
| Date | 2014-02-26 15:18 +0000 |
On Wed, 26 Feb 2014 11:00:34 GMT, anton@mips.complang.tuwien.ac.at (Anton Ertl) wrote: >stephenXXX@mpeforth.com (Stephen Pelc) writes: >>While I agree that multiple buffers for S" and S\" are useful, RAM >>is very limited on embedded systems, even those that have file >>systems. Even on 32 bit embedded systems, we run out of RAM long >>before we run out of Flash space. We are not going to use more >>RAM just to ease the very occasional interactive use of RENAME-FILE. > >Two ways out: > >1) We leave the number of buffers at one; users can write standard >code for interpretive use of RENAME-FILE that uses PARSE or PARSE-NAME >such as > >parse-name file1 s" file2" rename-file > >(or they write non-standard code). > >2) We standardize "at least two" buffers, and systems that don't want >to provide that have an environmental restriction. I suspect that most embedded system Forths already have environmental restrictions, so adding another one makes little difference. In the longer term, standardising an embedded subset of Forth200x may be a good thing to do. Stephen -- Stephen Pelc, stephenXXX@mpeforth.com MicroProcessor Engineering Ltd - More Real, Less Time 133 Hill Lane, Southampton SO15 5AF, England tel: +44 (0)23 8063 1441, fax: +44 (0)23 8033 9691 web: http://www.mpeforth.com - free VFX Forth downloads
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
RfD: Interpret S\" "Peter Knaggs" <pjk@bcs.org.uk> - 2014-02-25 01:14 +0000
Re: RfD: Interpret S\" "Alex McDonald" <blog@rivadpm.com> - 2014-02-25 08:26 +0000
Re: RfD: Interpret S\" stephenXXX@mpeforth.com (Stephen Pelc) - 2014-02-25 09:29 +0000
Re: RfD: Interpret S\" m.a.m.hendrix@tue.nl - 2014-02-25 03:43 -0800
Re: RfD: Interpret S\" Bernd Paysan <bernd.paysan@gmx.de> - 2014-03-04 02:46 +0100
Re: RfD: Interpret S\" albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-02-25 12:25 +0000
Re: RfD: Interpret S\" anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2014-02-26 11:00 +0000
Re: RfD: Interpret S\" stephenXXX@mpeforth.com (Stephen Pelc) - 2014-02-26 15:18 +0000
Re: RfD: Interpret S\" "Elizabeth D. Rather" <erather@forth.com> - 2014-02-26 08:28 -1000
Re: RfD: Interpret S\" Mikael Nordman <oh2aun@gmail.com> - 2014-02-26 12:33 -0800
Re: RfD: Interpret S\" anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2014-02-27 15:00 +0000
Re: RfD: Interpret S\" Andrew Haley <andrew29@littlepinkcloud.invalid> - 2014-02-25 04:55 -0600
Re: RfD: Interpret S\" anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2014-02-26 11:53 +0000
csiph-web