Xref: utzoo comp.unix.xenix:3647 comp.unix.wizards:11745 comp.lang.c:13278
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!ucsd!ucsdhub!esosun!seismo!uunet!ispi!jbayer
From: jbayer@ispi.UUCP (id for use with uunet/usenet)
Newsgroups: comp.unix.xenix,comp.unix.wizards,comp.lang.c
Subject: Far pointer problem resolved
Keywords: far pointer
Message-ID: <220@ispi.UUCP>
Date: 14 Oct 88 15:29:36 GMT
Organization: Intelligent Software Products, Inc.
Lines: 30


My thanks to the following people who replied to my question about
far pointers:

Ariel A. Aloni		att!ctsmain!raphel!ariel
Mark @			...!gatech!ncrats!iccdev!mark
John Owens		john@jetson.UPMA.MD.US		uunet!jetson!john
Jayen Vaghani		{uunet,ukc,ubc-cs,mcvax}!munnari.oz!jayen
Mike Howard		uunet!milhow1!how
Ragnar Paulson 		...utzoo!lsuc!dvlmarv!tsgfred!ragnar
Dr. T. Andrews		...!bikini.cis.ufl.edu!ki4pv!cdis-1!tanner  ...!bpa!cdin-1!cdis-1!tanner


For those who asked why I was using far pointers, my program is using
Unix V shared memory.  On Xenix 286, this type of shared memory is
accessed by far pointers.

The solution which was suggested by most of the above people was:

	return ( (struct abc far *)&ptr[x] ) ;

This eliminated the warning messages.  A few people also suggested 
simply ignoring the warnings.  It appeared that the code was being 
generated correctly.   I was concerned since this code has to be portable
between different machines, and I do not like warning messages at all.

Again, thanks to all of you.

Jonathan Bayer
Intelligent Software Products, Inc.