Xref: utzoo comp.sys.mac.programmer:5581 comp.sys.mac.hypercard:1819
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!apple!oren@apple.com
From: oren@apple.com (Tim Oren)
Newsgroups: comp.sys.mac.programmer,comp.sys.mac.hypercard
Subject: Re: XFCN/XCMD string in MPW C v3.0
Message-ID: <1312@internal.Apple.COM>
Date: 12 Apr 89 16:40:43 GMT
Sender: usenet@Apple.COM
Organization: Apple Computer Advanced Technology
Lines: 22
References:<1264@internal.Apple.COM> <2774@pegasus.ATT.COM>

In article <2774@pegasus.ATT.COM> ech@pegasus.ATT.COM (Edward C Horvath) 
writes:
> NO! do NOT detach!  If you do, you will no longer be able to reacquire
> with Get(Named)Resource: after DetachResource, a call to
> Get(Named)Resource will get a fresh copy of the original resource, not 
the
> detached (and now orphaned!) copy.
> 
> Also, don't call ChangedResource unless you want changes to your globals
> retained in the resource.  This is almost certainly NOT what you want.
> I know, you didn't even THINK of calling ChangedResource until I
> mentioned it...

Right you are - detach is not the right thing.  That's what I get for 
posting without rechecking the original code :-)   And yes, we did try 
ChangedResource, but that's only a good idea if you want to make your 
globals persistant between runs - which could be very useful if you are 
saving something like user preferences...

Tim Oren  oren@apple.com
"As always, if you are caught or killed, the CEO will disavow all 
knowledge of your actions."