Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!pdn!tscs!tct!chip From: chip@tct.uucp (Chip Salzenberg) Newsgroups: comp.std.c++ Subject: Re: type/member tags Message-ID: <27DD1669.C42@tct.uucp> Date: 12 Mar 91 17:56:57 GMT References: <1399@culhua.prg.ox.ac.uk> <27D3E544.619A@tct.uucp> <4338@lupine.NCD.COM> Organization: Teltronics/TCT, Sarasota, FL Lines: 20 According to rfg@NCD.COM (Ron Guilmette): >In article <27D3E544.619A@tct.uucp> chip@tct.uucp (Chip Salzenberg) writes: >+The class name is already guaranteed to be unique (name equivalence >+and all that). What need of more? > >Not only are file-scope class names not guaranteed to be unique across >multiple independent compilation units (which may later be combined to >form a single program) but class names need not even be unique *within* >a single compilation unit. Quite right; I had forgotton about local types. On the other hand, I do not believe that avoidance of local types for persistent and/or transmitted data is too much to ask of a programmer, especially since such a restriction would avoid the need for two class names (lexical and unique). -- Chip Salzenberg at Teltronics/TCT , "Most of my code is written by myself. That is why so little gets done." -- Herman "HLLs will never fly" Rubin