Date: Thu Mar 09 2006 - 00:42:03 PST
998: I agree. In SV, there is no question, though there was a question in Verilog. 99: Yes and no. If you had an entire document of high English quality and one specific chapter with a lot of bad spelling and grammar, then it would make sense to file a specific issue on that particular chapter. That is roughly the case here. In the issue description, I mentioned the following specific problems: inconsistent and misspellings and incorrect entries (such as reference to $displayf), duplicate entries due to letter case ("QQ" and "qq" become separate index entries) or different wording. I fixed a lot of those in 1364-2001 Version C, but I was not able to copy those corrections to 1364-2005. In a merged document, those sections of text which are simply copied to the new document from 1364-2005 are going to have the same problems. There is also another difference between the index and the text body. The technical sub-committees do indeed review the text body, they don't normally review the index, which is a problem, and requires a special reminder. Shalom ________________________________ From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of Rich, Dave Sent: Tuesday, March 07, 2006 6:47 PM To: sv-bc@eda.org Subject: RE: [sv-bc] Suggested items for email vote ________________________________ From: Bresticker, Shalom [mailto:shalom.bresticker@intel.com] Sent: Tuesday, March 07, 2006 4:05 AM To: Rich, Dave; sv-bc@eda.org Subject: RE: [sv-bc] Suggested items for email vote 998: What is the proposal? [DR>] The issue is a question which I answered as a bugnote. 999: I propose to postpone the issue on the basis that it should wait until after LRM merge. [DR>] I guess we will have to vote on this at a meeting. Unless you have specific problems that need proposals, this is just an action item. It no different than saying we need to review Clause 1, Clause 2 after they have been edited. 1002: I need to look at this. At one time, I had started working on a proposal which was a more significant rewording. 1005: I need to look at this. 1323: No opinion. Shalom ________________________________ From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of Rich, Dave Sent: Tuesday, March 07, 2006 9:20 AM To: sv-bc@eda.org Subject: [sv-bc] Suggested items for email vote I propose to take the following items to an e-mail vote. To streamline the process, I think it would be a good idea to discuss these items before actually beginning the e-mail vote to see if anyone has objections. <http://www.eda.org/svdb/bug_update_advanced_page.php?bug_id=0000998> 0000998 <http://www.eda.org/svdb/bug_view_page.php?bug_id=0000998> 1 <http://www.eda.org/svdb/bug_view_page.php?bug_id=0000998&nbn=1#bugnotes > V-1364 trivial assigned (bpierce) 12-21-05 10.2.2, 10.3.1: 'reg' keyword in tf port declarations <http://www.eda.org/svdb/bug_update_advanced_page.php?bug_id=0000999> 0000999 <http://www.eda.org/svdb/bug_view_page.php?bug_id=0000999> 2 <http://www.eda.org/svdb/bug_view_page.php?bug_id=0000999&nbn=2#bugnotes > V-1364 text assigned (shalom) 01-02-06 check index <http://www.eda.org/svdb/bug_update_advanced_page.php?bug_id=0001002> 0001002 <http://www.eda.org/svdb/bug_view_page.php?bug_id=0001002> 1 <http://www.eda.org/svdb/bug_view_page.php?bug_id=0001002&nbn=1#bugnotes > V-1364 text assigned (daver) 12-21-05 9.2: assignment variable_lvalue evaluation order question <http://www.eda.org/svdb/bug_update_advanced_page.php?bug_id=0001005> 0001005 <http://www.eda.org/svdb/bug_view_page.php?bug_id=0001005> 2 <http://www.eda.org/svdb/bug_view_page.php?bug_id=0001005&nbn=2#bugnotes > V-1364 feature assigned (daver) 12-23-05 4.2.1: Vector bit-select and part-select addressing <http://www.eda.org/svdb/bug_update_advanced_page.php?bug_id=0001323> 0001323 <http://www.eda.org/svdb/bug_view_page.php?bug_id=0001323> SV-BC tweak assigned (daver) 02-04-06 Clarifications needed for imported identifier access David Rich Verification Technologist Design Verification & Test Division Mentor Graphics Corporation dave_rich@mentor.com Office: 408 487-7206 Cell: 510 589-2625
