Hi Matthias,

Matthias Trute <mtr...@web.de> 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 Twain said, it is difficult to make
>   predictions, particularly about the future.
>
> ;)

Both guys didn't know what open source development, a labor of love, is
:-)

> 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.

> they change frequenctly only at development time. For
> applications the situation maybe different and that was
> the major driving force behind the recent changes.

>> 2. Will you provide some write-up?
>
> http://amforth.sourceforge.net/TG/recipes/Values.html should be a
> good starter. I'm working on it. Its more difficult to describe
> the possibilities than to implement them. As usual ...

I'd desire automatic cache initialization upon cached value
creation... need to think this through.

Keep up the good work, Thanks, Enoch.


------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amforth-devel

Reply via email to