Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!cbosgd!cbdkc1!desoto!packard!hoxna!houxm!vax135!cornell!uw-beaver!tektronix!decvax!genrad!panda!talcott!harvard!seismo!brl-tgr!tgr!MLY.G.SHADES%MIT-OZ@MIT-MC.ARPA
From: geoffrey dov cooper 
Newsgroups: net.lang.c
Subject: passing ptrs to statics
Message-ID: <8067@brl-tgr.ARPA>
Date: Tue, 5-Feb-85 22:13:40 EST
Article-I.D.: brl-tgr.8067
Posted: Tue Feb  5 22:13:40 1985
Date-Received: Sun, 10-Feb-85 03:33:18 EST
Sender: news@brl-tgr.ARPA
Organization: Ballistic Research Lab
Lines: 20


	the question of passing ptrs to statics started, as i seem to
remember (i deleted the mail already), with the fact that some
specific 8086 compiler optimized the calls to be intra-segment.  this
is as it should be; good optimization.  however the ptr that is 
generated by the c compiler should be a full ptr, i.e. segment and
offset.  if this is not the case then the compiler is defective.  a
static variable, which a function address can be, is defined as static
to limit the scope of the variable name and define the data as being
permanent not automatically allocated.  therefore the address of any
static is viable for passing.

	i suspect that the problem being encountered is something on
the order of "extern static  ".  if this is the case
then the static declaration should be deleted.

                           hope this helps

                      shades%mit-oz@mit-mc.arpa
-------