On Thu, Aug 13, 2009 at 4:56 AM, John A. De Goes <j...@n-brain.net> wrote:
> > The next step is to distinguish between reading file A and reading file B, between reading file A and writing file A, between reading one part of file > A and writing another part of file A, etc. When the effect system can carry > that kind of information, and not just for files, but network, memory, etc., > then you'll be able to do some extremely powerful parallelization & > optimization. > What if you have another program, written in C or something, that monitors a file for changes, and if so changes the contents of another file? Surely to catch that you must mark *all* file system access as "interefering"? Even worse, another program could monitor the state of a file and conditionally disable thet network driver, now file access interferes with network access. -- Sebastian Sylvan
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
