Regarding several recent responses to this thread: 1. Can you explain why memory references are very slow but accessing global caches (which is stored in memory) is very fast? Aren't they both references to memory?
2. New programmers should stay away from indirection. You can easily get into trouble very fast. Learn the basics of the M language and the use of VistA API tools first. Then as time permits, pursue understanding of indirection. 3. Without indirection, there would be no Fileman Database application. ----- Original Message ----- From: "Gregory Woodhouse" <[EMAIL PROTECTED]> To: <hardhats-members@lists.sourceforge.net> Sent: Wednesday, August 24, 2005 9:50 PM Subject: Re: [Hardhats-members] All about programming ...lot of memory references, and memory references are VERY slow, but a > strategy called caching, where recently accessed values are stored > for fast lookup. Unlike the data structure I described before, this > kind of caching is typically done in hardware, but there are software > caches, too, and it's software caches that makes global references in > MUMPS fast. > === > Gregory Woodhouse ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
