Thanks Wim Veldhuis for your msg about 16-Bit To 32-Bit Callbac, on
Sunday, 11-20-1994!

WV> I think this is bad. It breaks the rule that a typecast 
WV> does not alter the actual bytes, just the interpretation of 
WV> them. If CSet does this it would almost surely mean that 
WV> the code you produced is non-portable, even not to another 
WV> c

Actually it DOES change the actual bytes, because the 'actual bytes'
in this case IS the pointer. You are not casting the data pointed to,
just the pointer from a 32 bit to a 16 bit pointer (or the other way.)
And yes, the code is unportable, but not for the reasons you mention.
It is unportable because 16 bit code is basically unportable to the
rest of the computing world.

WV> OTOH if it is done during the assignment, it would mean an
WV> overloaded  operator= is used which is standard C++ (although not
WV> all  RTL supply it), but it would not require a cast. 

Its not an overloaded assignment operator, it is just the compiler
chosing to generate the code for you. It works in straight C as well as
in C++.

___
 X KWQ/2 1.2b X This tagline stolen by KWQ Mail/2.

--- Maximus/2 2.02