> Based on today's SV-EC meeting, the following is > a preliminary description of some rules Gord's outline exactly matches my understanding and seems to me to be a very neat and appropriately conservative specification. If this were implemented, it would become my preferred way to write *all* out-of-body subprograms, not just those with templated return types. My only (very tiny) reservation is about the use of the "extern" keyword. (And yes, I know that all this is different again in C[++]). In an "extern function" prototype, the extern prefix means "Here's a promise that in due course I will supply the details". In "extern class", the prefix means "I'm delivering on my earlier promise". At first I thought it would be a good idea to write "class extern" to emphasise that difference but, when I see the two options written down, I really don't like "class extern" at all. And I can't see an alternative way to say it without causing a lot of other trouble. So I think I'm happy to live with the small irregularity in those two meanings of extern. -- Jonathan Bromley, Consultant DOULOS - Developing Design Know-how VHDL * Verilog * SystemC * e * Perl * Tcl/Tk * Project Services Doulos Ltd. Church Hatch, 22 Market Place, Ringwood, Hampshire, BH24 1AW, UK Tel: +44 (0)1425 471223 Email: jonathan.bromley@doulos.com Fax: +44 (0)1425 471573 Web: http://www.doulos.com The contents of this message may contain personal views which are not the views of Doulos Ltd., unless specifically stated. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Tue Jun 26 01:02:28 2007
This archive was generated by hypermail 2.1.8 : Tue Jun 26 2007 - 01:04:58 PDT