Article View: comp.std.c++
Article #1059Re: "module" facility for top-level namespace control
From: Reid Ellis
Date: Mon, 29 Apr 1991 17:40
Date: Mon, 29 Apr 1991 17:40
17 lines
1161 bytes
1161 bytes
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>
};
Reid
-- still red from not seeing
-- the "static class {} var;"
-- option. :)
--
Reid Ellis 1 Trefan Street Apt. E, Toronto ON, M5A 3A9
rae@utcs.toronto.edu || rae@alias.com
CDA0610@applelink.apple.com || +1 416 362 9181 [work]
Technical Details
Message-ID:
<1991Apr29.174033.29627@alias.com>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!torsqnt!geac!alias!raeReferences:
<1991Apr19.163253.22253@kestrel.edu> <1991Apr19.183922.1982@kodak.kodak.com> <5143@lupine.NCD.COM> <1358@appli.se> <1991Apr25.060721.12694@alias.com> <RAEBURN.91Apr26165646@watch.mit.edu>Show Full Headers
Complete Article Headers
Newsgroups: comp.std.c++ Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!torsqnt!geac!alias!rae From: rae@alias.com (Reid Ellis) Subject: Re: "module" facility for top-level namespace control Message-ID: <1991Apr29.174033.29627@alias.com> Sender: news@alias.com (USENET News) Organization: Alias Research, Inc. Toronto ON Canada References: <1991Apr19.163253.22253@kestrel.edu> <1991Apr19.183922.1982@kodak.kodak.com> <5143@lupine.NCD.COM> <1358@appli.se> <1991Apr25.060721.12694@alias.com> <RAEBURN.91Apr26165646@watch.mit.edu> Distribution: comp.std.c++ Date: Mon, 29 Apr 91 17:40:33 GMT