Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ncoast.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!cwruecmp!atvax!ncoast!bsa
From: bsa@ncoast.UUCP (Brandon Allbery (the tame hacker on the North Coast))
Newsgroups: net.lang.c
Subject: Re: External names in other languages
Message-ID: <559@ncoast.UUCP>
Date: Thu, 24-Jan-85 01:38:34 EST
Article-I.D.: ncoast.559
Posted: Thu Jan 24 01:38:34 1985
Date-Received: Sun, 27-Jan-85 04:59:29 EST
References: <7332@brl-tgr.ARPA>
Reply-To: bsa@ncoast.UUCP (Brandon Allbery (the tame hacker on the North Coast))
Organization: The North Coast Xenix System, Cleveland
Lines: 21
Summary: 

> Article <7332@brl-tgr.ARPA>, from MLY.G.SHADES%MIT-OZ@MIT-MC.ARPA
+----------------
| 	it is a sound idea admittedly but it seems to me that all you
| are doing is the standard(?) practice of
| 
| #define this_is_a_very_long_name xyzzy
| int this_is_a_very_long_name;

Which works fine if the name happens to only contain characters legal
in C identifiers.  IBM 370 labels can contain $, #, and @.  The first
is allowed in SOME C implementations; the other two are allowed in no
C that I know of.  You can't #define

#define ibm_370_ext_func SYS#FOO$

--bsa
-- 
   Brandon Allbery @ decvax!cwruecmp!ncoast!bsa (..ncoast!tdi1!bsa business)
6504 Chestnut Road, Independence, Ohio 44131  +1 216 524 1416 (or what have you)
     Who said you had to be (a) a poor programmer or (b) a security hazard
			       to be a hacker?