Re: rpcrt4: Remove unreachable code in EmbeddedComplexSize.

2008-08-17 Thread Rob Shearman
2008/8/18 James McKenzie <[EMAIL PROTECTED]>: > Juan Lang wrote: >> Hi James, >> >> RPC_FC_ERROR_STATUS_T has a value of 0x10 and therefore isn't a possible value of "flags_type & 0xf" in the switch statement. >>> This may be a really stupid question, but is it possible to generate >

Re: rpcrt4: Remove unreachable code in EmbeddedComplexSize.

2008-08-17 Thread James McKenzie
Juan Lang wrote: > Hi James, > > >>> RPC_FC_ERROR_STATUS_T has a value of 0x10 and therefore isn't a >>> possible value of "flags_type & 0xf" in the switch statement. >>> >> This may be a really stupid question, but is it possible to generate >> this condition? >> > > No, it isn't po

Re: rpcrt4: Remove unreachable code in EmbeddedComplexSize.

2008-08-17 Thread Juan Lang
Hi James, >> RPC_FC_ERROR_STATUS_T has a value of 0x10 and therefore isn't a >> possible value of "flags_type & 0xf" in the switch statement. > > This may be a really stupid question, but is it possible to generate > this condition? No, it isn't possible. 0xf & (any value) will never produce any

Re: rpcrt4: Remove unreachable code in EmbeddedComplexSize.

2008-08-17 Thread James McKenzie
Rob Shearman wrote: > RPC_FC_ERROR_STATUS_T has a value of 0x10 and therefore isn't a > possible value of "flags_type & 0xf" in the switch statement. > Rob: This may be a really stupid question, but is it possible to generate this condition? James McKenzie