RE: [sv-ec] Status update for sv-ec ballot comments

Neil,

19 is strongly related to http://www.eda-stds.org/svdb/view.php?id=2632 .

81 is SV-AC http://www.eda-stds.org/svdb/view.php?id=2717 .

121 could be directly resolved by the editor, because the text immediately following the problematic line makes clear that a constant_expression is indeed required, as specified in A.2.11.


For ballot comment 56, I think it's safe to assume that it was just calling out Mantis 2380.

   "LRM is contradictory on whether unpacked array assignment requires element type equivalence or assignment compatiblity. See Mantis 2380."

   (BTW on May 11, 2009, SV-BC moved 2380 to SV-EC, mentioned in

    http://www.eda-stds.org/sv-ec/hm/6799.html
    http://www.eda.org/sv-bc/minutes/sv-bc_09_05_11.txt )


-- Brad


-----Original Message-----
From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Neil Korpusik
Sent: Tuesday, May 19, 2009 5:39 PM
To: SV_EC List
Subject: [sv-ec] Status update for sv-ec ballot comments

I have been going through all of the 1800-2009 ballot feedback that was
assigned to the sv-ec to make sure that everything was being tracked.
Mantis 2736 has been updated with all of the mantis items that remained in
the sv-ec for ballot comments. Everything that was approved by the svec
has been moved to the resolved state.

Attached is a list of all of the ballot comments that were processed by
the sv-ec.

As a result of this exercise I ended up with a couple of questions:

1. Mantis 2380

    Is the intent for it to also cover ballot id 56?
    Ballot id 56 was originally assigned to the sv-bc.

2. Mantis 2575

    Is the intent for it to also cover ballot id 64?

I ran out of time for today, but it looks like we need to create 4 more
mantis items for ballot id: 19, 53, 81, 121. I was unable to locate mantis
items for those.


Neil

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