Path: utzoo!utgpu!water!watmath!clyde!att-cb!ihnp4!ptsfa!ames!ucsd!hub!angst%csilvax
From: angst%csilvax@hub.ucsb.edu (The Stinkpuff)
Newsgroups: comp.lang.c
Subject: Re: do you like?
Summary: YES
Message-ID: <373@hub.ucsb.edu>
Date: 20 Feb 88 00:39:26 GMT
References: <906@PT.CS.CMU.EDU>
Sender: news@hub.ucsb.edu
Reply-To: angst%csilvax@hub.ucsb.edu
Organization: ///Club Angst!\\\
Lines: 30

In article <906@PT.CS.CMU.EDU> edw@IUS1.CS.CMU.EDU (Eddie Wyatt) writes:
>  I'm soliticing  comments on two new macro I added to my repetoire of
>useful things.
>
>#define IMPORT(from)    extern
>#define EXPORT(to)     
>
>example of usage:
>
>IMPORT (geometry.c) 		TOKEN vw_trans_at();
>EXPORT (tokenf.c main.c) 	void add_to_frametable();

Yes!  I like them.  I usually use

#define import		extern
#define export

but yours are better, in my humble opionion.

BTW, other useful macros for information hiders/software engineers are:

#define private		static		/* function or variables */
#define public				/* same */
#define procedure	void		/*

Comments?

Dave Stein                     Running without aim through the razor weeds that
angst%csilvax@hub.ucsb.edu     only reach my knees.   And when I'm lying in the 
...ucbvax!hub!csilvax!angst    grey sleep, I don't know how to walk the boards.