RE: [sv-bc] Please respond with your #1 SV-BC enhancement priority (due by end of January)

(My personal opinion, not necessarily Mentor's Official)

   The trend I am seeing talking to my customers is people wanting to
have SV code that is portable between EDA tools. So not only are they
trying to limit themselves to LRM compliant coding styles, but also
limit themselves to code constructs that work and work the same in most
if not all of the major simulation implementations.
   Therefore, at least in the SV-BC space I think its worth putting at
least some effort into the areas that are causing implementations to
diverge on functionality

  A specific area I'll mention is with macros and other preprocessor
stuff.
  Specifically mantis 1537

~Alex

-----Original Message-----
From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of Brad
Pierce
Sent: Tuesday, January 26, 2010 1:00 PM
To: sv-bc@eda.org
Subject: [sv-bc] Please respond with your #1 SV-BC enhancement priority
(due by end of January)

Background 1: http://www.eda-stds.org/sv-ieee1800/hm/0956.html
Background 2: http://bit.ly/7RDGox
Background 3: http://tinyurl.com/sv-bc-enhancement-requests

Because of the reasons in the above links, Matt and I need your feedback
on what SV-BC subscribers consider to be their #1 SV-BC enhancement
priority for the next revision, and why. We'll roll it up into a short
presentation to the Working Group.

The rules --

   0) This a public process, so all replies go to the reflector, not
just to Matt or me.
   1) You must include the number of a Mantis item. If your #1 issue is
not yet in Mantis, add it first, or get someone to add it for you.
   2) You must include a reason why this enhancement is critical for
users.
   3) Replies due by end of January.
   4) If you believe no SV-BC enhancements should be made in the next
revision, that's an OK answer, but it needs a reason, too.

Thanks for your help,
    
-- Brad

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