From -697327313566949868 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,a717e2be944aa399 X-Google-Attributes: gidf78e5,public X-Google-ArrivalTime: 1993-04-11 11:13:45 PST Newsgroups: comp.std.c++ Path: gmd.de!newsserver.jvnc.net!howland.reston.ans.net!agate!dog.ee.lbl.gov!network.ucsd.edu!munnari.oz.au!titan!trlluna!bruce.cs.monash.edu.au!merlin!mel.dit.csiro.au!its.csiro.au!dmssyd.syd.dms.CSIRO.AU!metro!news From: maxtal@physics.su.OZ.AU (John Max Skaller) Subject: Re: a library construction issue - forward references to nested classes Message-ID: <1993Apr11.140408.25891@ucc.su.OZ.AU> Sender: news@ucc.su.OZ.AU Nntp-Posting-Host: physics.su.oz.au Organization: School of Physics, University of Sydney, Australia References: Date: Sun, 11 Apr 1993 14:04:08 GMT Lines: 37 In article derek@watson.ibm.com (Derek Lieber) writes: > >My question is: what, if anything, does the ANSI committee >say about forward references to nested classes? Are they to >be allowed? Yes. >It seems to me that without such capability it is impossible to >properly manage a large namespace (ie. by decomposing it into >heirarchies of library classes in such a way as to avoid name collisions). > >Comments? > There is a separate proposal for namespace management. namespace X { f(); } using namespace X; int i=f(); namespace X { g(); } int j=g(); // OK! namespace Y { k(); } int l=Y::k(); namespace { int w; // 'static' not needed! }; Will this help? -- JOHN (MAX) SKALLER, INTERNET:maxtal@suphys.physics.su.oz.au Maxtal Pty Ltd, CSERVE:10236.1703 6 MacKay St ASHFIELD, Mem: SA IT/9/22,SC22/WG21 NSW 2131, AUSTRALIA