home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pmafire!news.dell.com!swrinde!zaphod.mps.ohio-state.edu!howland.reston.ans.net!usc!sdd.hp.com!nigel.msen.com!heifetz!tbomb!time
- From: time@ice.com (Tim Endres)
- Newsgroups: comp.sys.mac.programmer
- Subject: Re: Calling external code resources - how?
- Date: Mon, 25 Jan 93 15:59:44 EST
- Organization: ICE Engineering, Inc.
- Message-ID: <1CE00001.ojfngy@tbomb.ice.com>
- Reply-To: time@ice.com (Tim Endres)
- X-Mailer: uAccess - Macintosh Release: 1.6v2
- Lines: 21
-
-
- In article <1993Jan25.005216.12749@kth.se> (comp.sys.mac.programmer), d88-jwa@dront.nada.kth.se (Jon WΣtte) writes:
- > >Where can I find information on how to do this? The Segment Manager
- > >chapter of IM gives no clues on this. Anyone has got some sample code
- > >on this?
- >
- > Your extensions can't get at your globals, however,
- > you're not lost.
-
- uAccess extensions can get at the globals of uAccess. These globals
- have been placed inside of a large data structure inside of uAccess
- and uAccess hands a pointer to this structure to the extension. The
- globals in this data structure are only those that it is felt the
- extension would need to access, and are "stable" enough to be locked
- down to a documented data structure. However, it does make for some
- very powerful possibilities.
-
-
- tim endres - time@ice.com (UUCP: heifetz!tbomb!time)
-
- USENET - a slow moving self parody... ph
-