Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-lcc!ames!pasteur!ucbvax!decwrl!labrea!rutgers!att!lzaz!lznh!ariel
From: ariel@lznh.UUCP (<10000>Ariel Aloni)
Newsgroups: comp.lang.c
Subject: Re: Subroutine layout in C
Keywords: Here's a couple of handy macros...
Message-ID: <1987@lznh.UUCP>
Date: 6 Jan 89 15:44:22 GMT
References: <2459@ssc-vax.UUCP>
Reply-To: ariel@lznh.UUCP (<10000>Ariel Aloni)
Organization: AT&T, Lincroft, NJ
Lines: 24

In article <2459@ssc-vax.UUCP> dmg@ssc-vax.UUCP (David Geary) writes:
>
>  Frank is correct, this is exactly what you want to do.  However, I like
>to do the following:
>
>#define PRIVATE static
>#define PUBLIC 
> ...
Sure, this thing has no end, why not :

#define TINY short
#define HUGE long
#define RECORD struct
..... :-)

C is terse and accurate, if you want to invent new keywords for C
please don't abuse CPP, design your own new language.
In your particular example the change of 'static' is very confusing
since 'static' has a different meaning for functions and variables.

ariel

-- 
Ariel A. Aloni                                 att!lznh!ariel