home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!wupost!gumby!kzoo!k044477
- From: k044477@hobbes.kzoo.edu (Jamie R. McCarthy)
- Newsgroups: comp.sys.mac.programmer
- Subject: Re: dereferencing Handles( was Re: incrementation differences...)
- Message-ID: <1992Aug25.201711.19303@hobbes.kzoo.edu>
- Date: 25 Aug 92 20:17:11 GMT
- References: <1992Aug25.150911.19008@bnr.ca> <1992Aug25.161818.8069@hobbes.kzoo.edu> <1992Aug25.182750.13186@qualcomm.com>
- Organization: Kalamazoo College
- Lines: 25
-
- sdorner@qualcom.qualcomm.com (Steve Dorner) writes:
- >k044477@hobbes.kzoo.edu (Jamie R. McCarthy) writes:
- >>Unless you call Toolbox routines
- >>that move memory, the block will never move.
- >
- >1. Don't trust any list of toolbox routines that supposedly don't move
- >memory. People patch stuff, and s**t happens. Code defensively.
-
- While I admit to not having considered this, it seems to me that anyone
- who applies a memory-moving patch to a non-memory-moving trap is a
- Miscreant In The First Degree. A lot of interrupt code relies on those
- appendices being right! I mean, yeah, I'm all in favor of defensive
- coding, but this is going a little too far...
-
- Or am I out of touch, and people have been doing this for years?
-
- >2. Be aware that function calls to an unloaded segment may move memory,
- >(division of longs on 68000's is one such...)
-
- Ouch. A painfully good example.
- --
- Jamie McCarthy Internet: k044477@kzoo.edu AppleLink: j.mccarthy
- "It's bad enough to send a rude message to another via such an anonymous
- channel [as email]. To flame someone on an open forum is, to me, the
- height of insensitivity." - P.J. Plauger
-