🚀 go-pugleaf

In article <VANDEVOD.95Oct30181524@avs.cs.rpi.edu>,
vandevod@cs.rpi.edu (David Vandevoorde) wrote:

|> MR> What about the use of a typedef name from the class.  No size or
|> MR> layout is needed.  Example:
|> [example elided ...]
|> 
|> Good point. I thought it shouldn't (necessarily) require instantiation
|> of the typedef-enclosing class, but my favo(u)rite compiler says
|> otherwise (with your particular example)... and its designers are very 
|> knowledgeable in this area.
|> 
|> Anyone care to comment?

I'd go with your compiler designers on this one: to get the type of a class
member, you'd have to instantiate the class. There's a paper being written
on this topic (when types are required to be complete) which should be
voted on in March '96. Classes are required to be instantiated exactly when
the class type is required to be complete (plus a couple of other, explicit
uses such as in pointer to class casts). If the WP isn't clear enough on
this, well, we're still working on it!



--
         You must be out of your brilliant mind - Furniture
                 http://uptown.turnpike.net/~scorf


---
[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]