Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!unisoft!bdt!david
From: david@bdt.UUCP (David Beckemeyer)
Newsgroups: comp.sys.atari.st
Subject: Re: Open Files at AC_CLOSE
Keywords: DeskAccessory, File, AC_CLOSE
Message-ID: <606@bdt.UUCP>
Date: 27 Jun 89 00:04:57 GMT
References: <1158@gmdzi.UUCP> <1574@atari.UUCP> <599@bdt.UUCP> <1583@atari.UUCP>
Reply-To: david@bdt.UUCP (David Beckemeyer)
Organization: Beckemeyer Development Tools, Oakland, CA
Lines: 23

In article <1583@atari.UUCP> apratt@atari.UUCP (Allan Pratt) writes:
>In article <599@bdt.UUCP> david@bdt.UUCP (David Beckemeyer) writes:
>> Do I hear you saying "Nah, that probably won't ever happen?"
>
>No, you heard someone say, "If you change something, change it back
>before you let the mainline program run!"

Right. That was my main point.   You'll notice my posting said:
things can go wrong "if the ACC doesn't restore things."

I know there are ways to save/restore most things - but the person writing
the Desk Accessory has to use them.   My point was that the author of the
desk accessory must consider all the "context sensitive" things.  The DTA
and current directory were just two examples - there are many others
and not all are related to GEMDOS.

I've heard a lot of people say "Nah, ..." and ignore these psuedo
concurrency issues and that's why I mentioned it.
-- 
David Beckemeyer (david@bdt.UUCP)	| "Adios amigos.  And, as they say when 
Beckemeyer Development Tools		| the boys are scratching the bad ones,
478 Santa Clara Ave. Oakland, CA 94610	| 'Stay a long time, Cowboy!'"
UUCP: {uunet,ucbvax}!unisoft!bdt!david	|                  - Jo Mora