home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: chang.unx.sas.com!walker
- From: walker@chang.unx.sas.com (Doug Walker)
- Subject: Re: SAS/C 6.50 near and far
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Message-ID: <DLMwHJ.LFw@unx.sas.com>
- Date: Tue, 23 Jan 1996 12:39:19 GMT
- X-Nntp-Posting-Host: chang.unx.sas.com
- References: <4dsfg6$hrr@fnnews.fnal.gov>
- Organization: SAS Institute Inc.
-
- In article <4dsfg6$hrr@fnnews.fnal.gov>,
- Eric G. Stern <egstern@beatrice.fnal.gov> wrote:
- >In SAS/C 6.50+ does anyone know under what circumstances (if any) it
- >is permissable to link object files compiled with data=far with a
- >library that is compiled with the default option for data= .
- >
- > Eric Stern
-
-
- Yes, I know.
-
-
-
-
-
-
-
-
- Ok, ok, I guess I should't just leave it at that, eh?
- It should work fine to mix data= options as long as
- you do the following:
-
- *) Make sure to use __saveds to set up A4 correctly
- as appropriate, including entry points to libraries,
- callback hooks, and any functions called from code
- compiled with DATA=FARONLY.
-
- *) Use the __near or __far keywords to mark any data
- items used in one type of module but declared in
- the other type. That is, if you define an extern
- in a module compiled with DATA=FAR, it had better
- be declared in the near modules with the __far
- keyword, and vice-versa.
-
- *) Link with the SAS/C-provided FAR libraries, not the
- near ones.
-
- --
- ***** / walker@unx.sas.com
- *|_o_o|\\ Doug Walker< BIX, Portal: djwalker
- *|. o.| || \ AOL: weissblau
- | o |//
- ======
- Any opinions expressed are mine, not those of SAS Institute, Inc.
-
-