Re: [Amforth] The new VALUE implementation

2013-12-14 Thread Matthias Trute
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, >> I still see no need to protect DP and friends, since > > With DP and EDP, I agree, you are probably correct. Not so with > HERE as we should be able to call ALLOT as often as we desire. All memory manager I've seen so far avoid the primitive

Re: [Amforth] The new VALUE implementation

2013-12-13 Thread Enoch
Hi Matthias, Matthias Trute writes: > hH Enoch, > >> ... to cache EEPROM values in RAM. Two questions: >> >> 1. Will you apply this soon to "here"? > > pick at least one of the following > > Nostradamus allegedly said, “Prediction is >difficult, especially about the future.” > > As Mark T

Re: [Amforth] The new VALUE implementation

2013-12-13 Thread Matthias Trute
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hH Enoch, > ... to cache EEPROM values in RAM. Two questions: > > 1. Will you apply this soon to "here"? pick at least one of the following Nostradamus allegedly said, “Prediction is difficult, especially about the future.” As Mark Twain said

[Amforth] The new VALUE implementation

2013-12-13 Thread Enoch
Hello Matthias, I am very interested in your latest VALUE implementation and in particular, its ability to cache EEPROM values in RAM. Two questions: 1. Will you apply this soon to "here"? 2. Will you provide some write-up? If cache maintainance can be automatic i.e., loading from EEPROM on sta