Hi, It didn't sound like me, but it is well reasoned and I was flattered :) I agree that the use model is an issue that will likely grow with classes. My own view is that it needs to be solved and others like it. Whether we call it deferred or recast elaboration as multipass depends on what other problems we wish to address of this nature. This is one of the limitations on hierarchical references, for example. My only concern is whether this rises to the occasion as the time to address it and I thought it better to address during class model design. I would opt for avoiding special decl syntax and prefer semantic restriction on when during elaboration of the model it can be used. Regards, John Peter Ashenden wrote: > Dear colleagues, > > I inadvertently attributed a comment on IR2119 to John Shields. It was in > fact from John Ries. I apologise to both for the misattribution. > > Cheers, > > PA > > -- > Dr. Peter J. Ashenden peter@ashenden.com.au > Ashenden Designs Pty. Ltd. www.ashenden.com.au > PO Box 640 VoIP: sip://0871270078@sip.internode.on.net > Stirling, SA 5152 Phone: +61 8 7127 0078 > Australia Mobile: +61 414 70 9106 > > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Oct 31 22:24:49 2007
This archive was generated by hypermail 2.1.8 : Wed Oct 31 2007 - 22:26:45 PDT