Notes |
(0007251)
gordonv (developer)
2008-07-23 07:10
|
Fixed the "umtyped" typo per the 7/22 meeting. Also removed the note
to SC readers and deleted the old versions of the proposal. |
|
(0007252)
gordonv (developer)
2008-07-23 07:11
|
Proposal was approved in the 7/22 SV-SC meeting. |
|
(0007254)
Erik_Seligman (developer)
2008-07-23 09:28
|
Passed in voice vote at SV-SC meeting, 2008-07-22.
9y/1n/0a
Mark Hartoog votes no – not needed, creates backwards compatibility issues. Clarification – not 100% sure about the note at the end, but the whole basic idea of casting these expressions to their self-determined type has the potential to create very subtle backwards compatibility issues per the face-to-face. |
|
(0007280)
Neil Korpusik (administrator)
2008-08-01 18:27
|
The proposal was sent back to the SV-SC by the
Champions in the July 31st, 2008 conference call.
a. Page 2, 16.8, 2nd bullet, the change doesn't appear to be correct.
The previous language said that an exception is made for substitution of an
actual for a reference to the corresponding formal is made if
The reference to the formal argument stands as a variable_lvalue in
an operator_assignment or inc_or_dec_expression in a
sequence_match_item.
This has been changed to say
The actual argument is a variable_lvalue.
These two do not mean the same thing. I think that the actual could
be a variable_lvalue in cases for which we do not want this rule to apply.
I think that the original wording of this condition should be restored
(two places).
There appear to be some cases of variable_lvalue doesn't make sense. A
whole variable can be an lvalue, we don't want variables to hit this
exception.
16.8.1 there is another similar change, part in blue (last para)
b. We also now have an inconsistency between the new wording in 16.8 and
16.8.1 and the wording in the Annex F changes for 1549.
After the meeting John sent a followup email:
Gord explained to me that if vlv is a variable_lvalue, then
<self_determined_result_type_of_vlv>'(vlv)
behaves the same as vlv in all contexts.
Given this, I have no objection to his rewrite of the rules of the
exceptions for untyped arguments in 2434.
However, as far as I am aware, there remains an inconsistency between
2434 and the Annex F changes in 1549 and 1667 regarding these rules.
I think that 2434 ought to change the wording in in Annex F to align
with the new rules. |
|
(0007318)
Dave Rich (manager)
2008-08-07 09:17
|
uploaded change (declaration of b_d,d_d) from 8/7/08 champions meeting. |
|
(0007325)
Erik_Seligman (developer)
2008-08-13 09:44
|
SV-SC reviewed champion fix in 2008-08-12 meeting, no objections. |
|
(0007338)
Neil Korpusik (administrator)
2008-08-18 16:33
|
The proposal was unanimously approved by the Champions in the
August 7th, 2008 conference call with the following friendly amendments.
Friendly amendment:
- page 4 example, for clarity, the example should show where
b_d is declared.
Note: this change was made by Dave, during the Champion's meeting. |
|
(0007380)
Neil Korpusik (administrator)
2008-08-18 18:44
|
The proposal was unanimously approved by the Working Group
in the conference call of August 14, 2008.
|
|
(0007492)
Stuart Sutherland (manager)
2008-09-08 23:42
|
The change proposal was implemented in draft 7. |
|
(0007523)
gordonv (developer)
2008-09-15 14:30
|
In the draft 7 pdf, the following paragraph in 16.8 is crossed
out (not deleted) with a comment that it is related to 2434.
The supported data types for sequence formal arguments are the
types that are allowed for operands in assertion expressions
(see 16.6.1) and the keyword untyped.
This paragraph was not deleted by the 2434 proposal so it isn't
clear to me whether this was unintentional cross-out or intended
to be a editor suggestion.
If the cross-out is removed, the rest of the proposal looks to
be correctly applied.
|
|
(0007580)
Stuart Sutherland (manager)
2008-10-01 21:28
|
The changes requested in bug note 7523 were implemented in draft 7a. The strike-through line was removed and the paragraph left in the LRM. |
|
(0007788)
Neil Korpusik (administrator)
2008-12-19 18:05
|
I verified that the paragraph in question is contained in 1800-2009 draft 8.
Changing the status to closed. |
|