🚀 go-pugleaf

In article <1991May1.192611.20568@kestrel.edu> gyro@kestrel.edu (Scott Layson Burson) writes:

   From: gyro@kestrel.edu (Scott Layson Burson)
   Date: 1 May 91 19:26:11 GMT
   Distribution: comp.std.c++
   Organization: Kestrel Institute, Palo Alto, CA

   In article <1991Apr30.202357.13791@kestrel.edu> I wrote:
   >In article <1991Apr29.174033.29627@alias.com> rae@alias.com (Reid Ellis) writes:
   >>Why don't we simply use a syntax which already evokes this concept --
   >>using "extern"?
   >>
   >>I don't know if another keyword after the extern is necessary, or
   >>simply the name of the enclosing scope.  Something like the following?
   >>
   >>extern NIH {
   >>#include <NIHCL.h>
   >>};

   ...

   Oops -- Jerry Schwarz (jss@kpc.com) has corrected me -- the construct
   is rendered unambiguous by the `{'.  So this objection is invalid.

What about this one ?

#define NIH "C"