0002721: Ballot Comment #135: Ambiguity in treatment of bind statements in bound design elements

Notes
(0008066) gordonv (developer) 2009-04-27 10:27	Note - here is an example of something that the proposal makes explicitly illegal. I am in favor of this change. module top; endmodule bind top mid mid1(); module mid; bind mid bot bot1(); endmodule module bot; endmodule

(0008390) shalom (manager) 2009-05-31 05:44	I think this change may leave ambiguous the current last sentence in the clause: "It shall be an error for a bind statement to bind a bind_instantiation underneath the scope of another bind_instantiation." In fact, adding the proposed new sentence will make this sentence even less clear by excluding that possibility from its meaning. Should the proposal be to replace this sentence instead of just adding a new one?

(0008440) Steven Sharp (developer) 2009-06-01 17:04	I believe that the restrictions specified by the two sentences are different and orthogonal. The old sentence says that you cannot perform a bind into the hierarchy created by an earlier bind. You could have this error without having a bind statement in the hierarchy created by bind. You could have a bind statement that creates an instance c in instance b, followed by a second bind statement that tries to create an instance d in the newly created b.c. The new sentence says that you cannot have bind statements inside the hierarchy created by a bind statement. Such a nested bind statement might not be binding into the hierarchy created by the outer bind statement. It could be binding elsewhere in the design. It might be common to make both errors at the same time. The bind_instantiation might contain bind statements that try to bind into the hierarchy created by that bind_instantiation. But you could also make either error without the other, so they need to be specified separately.

(0008537) mmaidment (manager) 2009-06-15 10:18	On June 15, 2009 the SV-BC unanimously approved the following response: Currently the LRM supports bind statements in bound modules, provided the bind statements do not violate restrictions as currently defined in the LRM such as this one in 23.11: "It shall be an error for a bind statement to bind a bind_instantiation underneath the scope of another bind_instantiation."

(0008718) Dave Rich (manager) 2009-07-01 10:43	The Champions have voted unanimously to approve this issue on June 29, 2009

(0008850) Dave Rich (manager) 2009-07-02 15:17	The P1800-2009 Working Group approved the resolution of this issue as no change required.

Issue History
Date Modified	Username	Field	Change
2009-04-26 23:30	mmaidment	New Issue
2009-04-26 23:30	mmaidment	Type	=> Errata
2009-04-26 23:33	mmaidment	Relationship added	related to 0002685
2009-04-26 23:44	shalom	Relationship replaced	child of 0002685
2009-04-27 00:28	shalom	Issue Monitored: shalom
2009-04-27 10:27	gordonv	Note Added: 0008066
2009-04-27 14:10	Steven Sharp	File Added: nestbind.pdf
2009-04-27 14:12	Steven Sharp	Assigned To	=> Steven Sharp
2009-04-27 14:12	Steven Sharp	Priority	normal => immediate
2009-04-27 14:12	Steven Sharp	Status	new => assigned
2009-05-31 05:44	shalom	Note Added: 0008390
2009-06-01 17:04	Steven Sharp	Note Added: 0008440
2009-06-15 10:18	mmaidment	Note Added: 0008537
2009-06-15 10:18	mmaidment	Status	assigned => resolved
2009-06-15 10:18	mmaidment	Resolution	open => no change required
2009-07-01 10:43	Dave Rich	Note Added: 0008718
2009-07-02 15:17	Dave Rich	Note Added: 0008850
2009-07-02 15:19	Dave Rich	Status	resolved => closed