Path: utzoo!utgpu!water!watmath!clyde!att!ihnp4!cbmvax!vu-vlsi!devon!stb!michael
From: michael@stb.UUCP (Michael)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Another question on the 80286- er, 68000 memory models
Message-ID: <10354@stb.UUCP>
Date: 26 May 88 05:26:41 GMT
References: <8805182223.AA20918@cory.Berkeley.EDU> <2653@louie.udel.EDU> <2869@polya.STANFORD.EDU>
Reply-To: michael@stb.UUCP (Michael)
Organization: STB BBS, La, Ca, Usa, +1 213 459 7231
Lines: 20

In article <2869@polya.STANFORD.EDU> rokicki@polya.Stanford.EDU (Tomas G. Rokicki) writes:
>	  Always use 16-bit relative; no sense not to, since
>	  the long ones are taken care of automatically, and
>	  smaller code size is usually good.  Again, in

IF you are passing pointers to functions and using them for comparisons,
THEN you should (must?) use LARGE CODE model. (At least for large programs)

Reason: Otherwise, you will be comparing the address of the jump table
in some cases with the address of the routine itself in other cases.
(The pointer will still be 32 bits, but if you are close to the routine
you will get a pointer to the code, while if you are far, you will get a
pointer to the jump table. At least this was true in the past, and I think
its still true, never did check recently)
: --- 
: Michael Gersten			 uunet.uu.net!denwa!stb!michael
:				 ihnp4!hermix!ucla-an!denwa!stb!michael
:				sdcsvax!crash!gryphon!denwa!stb!michael
: "Machine Takeover? Just say no."
: "Sockets? Just say no."     <-- gasoline