Path: utzoo!utgpu!watserv1!watmath!att!att!emory!wuarchive!usc!elroy.jpl.nasa.gov!decwrl!mcnc!uvaarpa!murdoch!astsun.astro.Virginia.EDU!gl8f
From: gl8f@astsun.astro.Virginia.EDU (Greg Lindahl)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: Quien es mas macho? (HD caching)
Message-ID: <1990Nov1.055527.498@murdoch.acc.Virginia.EDU>
Date: 1 Nov 90 05:55:27 GMT
References: <13510003@hplsla.HP.COM> <1990Oct30.220831.17172@math.lsa.umich.edu> <6948@castle.ed.ac.uk>
Sender: news@murdoch.acc.Virginia.EDU
Organization: Department of Astronomy, University of Virginia
Lines: 15

In article <6948@castle.ed.ac.uk> ngse18@castle.ed.ac.uk (J R Evans) writes:

> At the same time,
>to the best of my knowledge, all the software caches for the ST are
>'write-through'.  This means that all files are actually written out
>to disk as they are made.  [Again, if there are 'intelligent' caches out
>there, given TOS's insecurity, *I* wouldn't risk my data by using them
>in a development environment].

Laser C has a file-level cache which is write-through for your source
code and delayed write-back for temporary files, object files, and
executables. It's amazingly easy to use, and much better than a RAM
disk as it's dynamic and you don't have to set anything up to use it.
On a 1 meg ST with floppies it must be a godsend -- even with a HD,
it's quite nice.