Hi, Since I took on the issue, and Yulik filed it after discussions with me, let me clarify. I have had no intention of changing any behavior, just of clarification of existing behavior. The phrase "input used as output" and its converse are ambiguous and have been often misinterpreted. The question of whether or not it is legal to assign to an input and what happens if you do so has also been repeatedly asked. Users will welcome any clarification of these subjects. Regards, Shalom > -----Original Message----- > From: Gordon Vreugdenhil [mailto:gordonv@model.com] > Sent: Monday, October 29, 2007 4:50 PM > To: Bresticker, Shalom > Cc: sv-bc@server.eda.org > Subject: Re: [sv-bc] E-mail Vote: Respond by 8am PDT, Monday, > October 29 - 1573 > > > > Brad Pierce wrote: > > Forcing port collapsing would not be backward compatible. > > > >> If there is > >> a desire to force implementations to coerce ports when > possible, then > >> there should be text saying that port collapsing must be done > >> whenever possible (and clarifying some of the cases where > it may not > >> be clear whether it is possible). > > > I think this exchange is at the core of all the objections. > 1364 allows either port coercion and collapsing in > implementations for historical reasons. The assumption is > that the two are "equivalent". That is not the case. There > are various cases that Steven and I have raised where that > assumption breaks down. Any change to require either > approach will cause serious objections from various vendors. > > Although I appreciate the desire to have a tighter LRM in > this area, I just don't think it is feasible. Given the time > remaining, I would suggest that we not spend further effort on this. > > Gord. > -- > -------------------------------------------------------------------- > Gordon Vreugdenhil 503-685-0808 > Model Technology (Mentor Graphics) gordonv@model.com > --------------------------------------------------------------------- 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.Received on Mon Oct 29 08:12:54 2007
This archive was generated by hypermail 2.1.8 : Mon Oct 29 2007 - 08:13:04 PDT