🚀 go-pugleaf

The attitude at least one correspondent takes -- read the volume control out
on every DA close, or even every systemclick -- is a bit naive.  The nature
of DAs as "asynchronous processes" makes it impossible to take account of
EVERYTHING they might do to you.

As a more extreme example, I am working on an application that maintains a
DeskTop image.  If you run the Extras DA you can delete a file.  Does this
suggest that I should rescan all volume directories on every system click,
just in case Extras or something like it removed a file?  Has anybody tried
doing this to FileVision (which retains 'back to...' in the file menu)?

Take a still more extreme example: postulate a DAMover DA.  Such a DA MIGHT
remove a DA from the System file.  So, I guess I had better reconstruct the
apple menu on every system click as well.  What have I missed?  An
irresponsible DA may clobber the System Font or one of my application fonts
on a system click...

How well will your last program run if some asynchronous process shoots out
its temp files on the fly?  Or overwrites them?  Do you recalculate
checksums on everything before you trust the data in the file?

You see the problem.  When is a "user-friendly" system allowed to give up
in the face of a hostile user?

=Ned=