-----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 ALLOT. They all use ALLOT once to get a larger memory pool and operate later within this pool only. Thus they can deal with fragmented memory which the stupid ALLOT simply cannot. Furthermore a typical microcontroller program tends to allocate RAM statically, so the burden of frequent changes of HERE is limited, it seems. Of course there are counter-examples.... The forth gurus recently talked about region memory management, an idea I could get used to. http://forth-ev.de/wiki/doku.php/en:events:euroforth-2013 > I'd desire automatic cache initialization upon cached value > creation... need to think this through. Sound like a good task for a traverse-wordlist in turnkey. I love lazy developers ;) Matthias -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKsYEMACgkQ9bEHdGEMFjORcACeI+fQl3Bl17AaQQvnBwUUyQs+ vSkAoLg3vi6haKCEoP/e3eOSTToL0sFR =MX+Y -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ 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
