RE: [sv-bc] Edge-sensitive paths with Mantis 1253

Hi,

You are quite correct!

This change was implemented in P1364-2008/Draft 1, still appeared in the merged P1800-2008/Draft 2, but somehow it disappeared in Draft 3!

The text change in Mantis 1253 does appear in the latest draft, though.

I feared there were other BNF changes in P1364-2008/Draft 1 that also disappeared, but I have checked and found that this was the only BNF change in that draft. So hopefully, this is the only mistake of that type.

And yes, SV-BC is the committee responsible for this clause.

Thanks,
Shalom

________________________________
From: owner-sv-bc@server.eda.org [mailto:owner-sv-bc@server.eda.org] On Behalf Of Surya Pratik Saha
Sent: Saturday, January 10, 2009 5:08 PM
To: sv-bc@eda.org
Subject: [sv-bc] Edge-sensitive paths with Mantis 1253

Hi,
I am not sure which alias is appropriate for this chapter, so I am using sv-bc. In the draft 2009 SV LRM, in syntax 30-4, there was tag of mantis 1253. But the syntax does not show the change proposed in the mantis. Is it a typo or something else?

Here is the syntax 30-4:
parallel_edge_sensitive_path_description ::=
( [ edge_identifier ] specify_input_terminal_descriptor =>
( specify_output_terminal_descriptor [ polarity_operator ] : data_source_expression ) )

And Mantis proposes:
parallel_edge_sensitive_path_description ::=
      ( [ edge_identifier ] specify_input_terminal_descriptor [ polarity_operator ] =>
         ( specify_output_terminal_descriptor [ polarity_operator ] : data_source_expression ) )
See the blue color one is missing, It is same for full_edge_sensitive_path_description.

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