I would argue on your both the points.
Quote:
|
Originally Posted by sureshN
-Why does the function take integer as the parameter and later converts it into unsigned char? The function could have accepted the parameter as ‘unsigned char’ directly.
|
As per MSDN its Character to set to the memory and so integer means the ASCII value of the character as an input and so the valid range is always a positive and so unsigned char is as desired.
when passing 0xAABBCCDD as second parameter its not what is expected (as MSDN clearly says what it does)