[sv-ec] Mantis 1715

hi EC,

Dav Rich raised a pertinent issue in his NO vote on 1715:

> An informative note this lengthy implies that the
> normative text is not clear enough, or this
> enhancement it not really justified.

Given the extreme pressure on committee time right now,
and given that the desiderata of 1715 can already be
achieved in the language as it stands (see below), I'd
like to suggest dropping this issue, or (better) 
postponing it for future consideration.  I've missed 
a couple of meetings and lost my voting rights, but 
perhaps someone could table this at Monday's meeting?


For the record... why 1715 is a luxury, not a necessity:

  event e_cb;

  clocking cb @(....); .... endclocking
  // now I can do @(cb) but not (cb.triggered),
  // nor can I do e_cb=cb;

  always @cb -> e_cb;  // clone @cb
  // now I can do (e_cb.triggered) and generally
  // mess with e_cb in any way I wish

-- 
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.