[sv-cc] SV-CC Action Item: Pls take another look at 2173, 2326, 2327

Hi SV-CC:

Can you guys try to take another look at these proposals before the Wed.
meeting, and see if we can get CC approval rather than having to refer
them to the new committee?
Thanks!

 

-----Original Message-----
From: owner-sv-cc@server.eda.org [mailto:owner-sv-cc@server.eda.org] On
Behalf Of John Havlicek
Sent: Monday, April 07, 2008 6:50 AM
To: Neil.Korpusik@sun.com; sv-ac@server.eda.org; sv-bc@server.eda.org;
sv-cc@server.eda.org; sv-ec@server.eda.org; ieee1800@server.eda.org
Cc: Bresticker, Shalom
Subject: Re: [P1800] RE: [sv-cc] New P1800 technical committee - Call
For Participation - reminder

Hi Folks:

I agree with Shalom.

2173, 2326, and 2327 add "case" as a property building construct within
concurrent assertions.  We already have "if-else", so this is primarily
syntactic sugar.

I do not think that these should be moved from SV-AC to the new
sub-committee

J.H.

> Hi,
> 
> > I think we should add to the list for this new committee (Erik)
> > 
> > 9.  2173
> > 10. 2326
> > 11. 2327
> 
> Is this Erik's personal request or an SV-AC request?
> Who decides what issues the new sub-committee deals with?
> 
> I don't think these are related to checkers or assertions in 
> procedural code, so I would be reluctant to have the new sub-committee

> deal with these as well. I think it would be a diversion and a 
> dilution of the work, which is going to be hard enough even without 
> these additional issues.
> 
> (It would be nice if this new sub-committee had a short name. It's 
> awkward saying "the new techical sub-committee" alll the time...)
> 
> Thanks,
> Shalom
> ---------------------------------------------------------------------
> Intel Israel (74) Limited
> 
> This e-mail and any attachments may contain confidential material for 
> the sole use of the intended recipient(s). Any review or distribution 
> by others is strictly prohibited. If you are not the intended 
> recipient, please contact the sender and delete all copies.
> 
> 
> --
> This message has been scanned for viruses and dangerous content by 
> MailScanner, and is believed to be clean.
> 
> 

--
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.