This is what I've ment. But imho implicit for should be deprecated or even removed to be consistent with function declaration. If it cannot be removed due to compability issues then maybe tool can print warning on such code that "extern" need to be added. DANiel -----Original Message----- From: jonathan.bromley@doulos.com [mailto:jonathan.bromley@doulos.com] Sent: 22 kwietnia 2009 19:29 To: sv-ec@server.eda.org Cc: Daniel Mlynek; Rich, Dave Subject: RE: [sv-ec] Ballot issue #182, Mantis 2514: Out of block constraints I've uploaded a (very) tentative proposal for Mantis 2514 as threatened, adding "pure" and "extern" keywords for constraint prototypes. Please take a look and let me know whether you think it is too disruptive for this stage in the process. I don't want to put any further work into something that won't find consensus. The alternative is probably just to normalize the existing de facto tool behavior, but the desired behavior for constraint prototypes in abstract classes would still need to be sorted out. Thanks -- Jonathan Bromley Consultant Doulos - Developing Design Know-how VHDL * Verilog * SystemVerilog * SystemC * PSL * 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 http://www.doulos.com ---------------------------------------------------------------------------- ---- Doulos Ltd is registered in England and Wales with company no. 3723454 Its registered office is 4 Brackley Close, Bournemouth International Airport, Christchurch, BH23 6SE, UK. This message may contain personal views which are not the views of Doulos, unless specifically stated. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Apr 22 23:51:09 2009
This archive was generated by hypermail 2.1.8 : Wed Apr 22 2009 - 23:51:19 PDT