> If "item" is being used as a class > member then "item.item" works and is such a unique special > case that I really don't think that it would be that > confusing, particularly if the LRM addresses it directly. Yes, but suppose someone today has a class with a member called "item" of struct type; then the following code will suddenly and miraculously change its meaning under the possible new "item." rule: typedef struct { int x; } S; class C; rand S item; rand int x; endclass ... C c; ... c.randomize() with {item.x > 3;}; I don't think that's an acceptable piece of collateral damage, even given that it's fairly unlikely. -- 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 Oct 23 07:27:26 2007
This archive was generated by hypermail 2.1.8 : Tue Oct 23 2007 - 07:27:33 PDT