[sv-bc] RE: [sv-ec] RE: areas of implementation divergence

Yes it does.

Typical cases are (1) that a user writes code for the tool he is using and then has problems when moving to another tool; (2) user writes code according to how he understands LRM and then it works differently than expected or not at all.

These happen to us frequently, especially (1).

Shalom

> -----Original Message-----
> From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Brad
> Pierce
> Sent: Tuesday, March 03, 2015 20:10
> To: sv-bc@eda.org; sv-ec@eda.org
> Subject: RE: [sv-ec] RE: areas of implementation divergence
> 
> Gord writes
> 
> >As Dave said, it would take a while to go through the (many!)
> >implementation divergences that we know about and figure
> >out which the committee would consider ambiguous vs
> >extensions/illegal behavior.  The ones I listed above are more
> >obviously ambiguous/inconsistent/incomplete.
> 
> Yet users get the job done every day. Ambiguity may
> be nettlesome to implementers, but does it really have
> a significant impact on usability?
> 
> I'd like to hear from users about issues where tool divergence
> gets in the way of productivity, and whether it gets in the way
> more so than does the lack of requested new language features.
> 
> -- Brad
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 
> 

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