Path: utzoo!mnetor!uunet!husc6!bbn!bbn.com!rsalz
From: rsalz@bbn.com (Rich Salz)
Newsgroups: comp.lang.c
Subject: Re: do you like?
Message-ID: <428@fig.bbn.com>
Date: 20 Feb 88 21:05:56 GMT
References: <906@PT.CS.CMU.EDU> <373@hub.ucsb.edu>
Organization: BBN Laboratories, Cambridge MA
Lines: 18

In article <906@PT.CS.CMU.EDU> edw@IUS1.CS.CMU.EDU (Eddie Wyatt) asks for
feedback on:
	#define IMPORT(from)    extern
	#define EXPORT(to)     
with this sample usage;
	IMPORT (geometry.c) 		TOKEN vw_trans_at();
	EXPORT (tokenf.c main.c) 	void add_to_frametable();

Cute, but I don't like them because they violate the "write once" rule.
If you move a routine, you have to remember to change the header file
where the #define's appear.

It's much better to use information abstractors on the primary source to
get the data you seek.  In less jargon, use ctags or something similar;
it was published in comp.sources.unix some while ago, and can be freely
redistributed.
-- 
For comp.sources.unix stuff, mail to sources@uunet.uu.net.