🚀 go-pugleaf

I wrote:
|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>
|};

Scott Layson Burson <gyro@kestrel.edu> writes:
|Oops -- Jerry Schwarz (jss@kpc.com) has corrected me -- the construct
|is rendered unambiguous by the `{'.  So this objection is invalid.

Robert Krajewski <robertk@lotatg.lotus.com> writes:
|What about this one ?
|
|#define NIH "C"

Is this a valid objection?  Anything can be #define'd to anything.  I
wouldn't think that possible preprocessor abuse would be a problem
unique to this situation.  It would be like saying

	What about "#define class struct"?

as an objection to the "class" keyword.

						Reid
--
Reid Ellis
rae@utcs.toronto.edu        ||               rae@alias.com
CDA0610@applelink.apple.com ||      +1 416 362 9181 [work]