Hm. Thanks for the heads up. Now how about
byte &= int is there any good reason why the result type of that isn't error? On 10/27/2010 10:12 PM, Steven Schveighoffer wrote:
On Wed, 27 Oct 2010 22:49:47 -0400, Ellery Newcomer <ellery-newco...@utulsa.edu> wrote:can someone remind why the resulting type is int? is it a "c does it" thing?Yes, but it should be reassignable to a byte via range propogation. With C, there was no range propogation, so int & int was also assignable to char. -Steve
