> >I think the relevant section is the LRM section 13.9.1
Just curious. Long, long ago, in a company far, far away,
we were NOT getting constraint error that we thought we
should at an assignment statement.
The vendor's argument was that if you traced back the origin of the right
side far enough, you'd find an unchecked conversion, therefore no checks
Our argument was that the compiler could not trace back that far, since
that would require all the bodies to be compiled at the same time as the
specs, therefore the compiler had no business skipping checks at the
various calls along the way.
Opinions? (not that it matters now)