home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!zaphod.mps.ohio-state.edu!cs.utexas.edu!sun-barr!ames!data.nas.nasa.gov!taligent!apple!lai
- From: lai@Apple.COM (Ed Lai)
- Newsgroups: comp.sys.mac.programmer
- Subject: Re: AEDisposeDesc
- Message-ID: <71728@apple.Apple.COM>
- Date: 27 Aug 92 16:34:01 GMT
- References: <w0bn2sb.mspace@netcom.com>
- Organization: Apple Computer Inc., Cupertino, CA
- Lines: 37
-
- In article <w0bn2sb.mspace@netcom.com> mspace@netcom.com (Brian Hall) writes:
- >Is it safe to call AEDisposeDesc on an AEDesc more than once? I "<noticed
- >that after the call, the AEDesc passed in had a type of "typeNull" and
- >a datahandle of "NULL". Does AEDisposeDesc know enough not to try and
- >dispose of a record like that?
-
- Whenever the dataHandle is NIL, AEDisposeDesc is a nop, since AEDisposeDesc
- changes the AEDesc to typeNull dataHandle nil after disposing, accidential
- calling AEDisposeDesc again would not hurt.
-
- >
- >On a related note, is it safe to call AEDisposeDesc when the AEDesc is
- >{0, NULL} (essentially 0,0)) instead of { typeNull, NULL}? This, of course,
- >assumes that it is OK to call AEDisposeDesc on {typeNull, NULL} in
- >the first place.
- >
-
- See above.
-
- >If it is not OK, I think I will end up making a ForgetAEDesc along
- >the lines of TCLs ForgetHandle routine.
- >
- >--
- >
- > \ | / | Brian Hall mspace@netcom.com
- > - : - | Mark/Space Softworks Applelink: markspace
- > /|\ | America Online: MarkSpace
- > |-+-| |
- >/-\|/-\ | Stupidity is its own punishment.
-
- /* Disclaimer: All statments and opinions expressed are my own */
- /* Edmund K. Lai */
- /* Apple Computer, MS37-UP */
- /* 20525 Mariani Ave, */
- /* Cupertino, CA 95014 */
- /* (408)974-6272 */
- zW@h9cOi
-