ZZ>
  > I think this is bad. It breaks the rule that a typecast
  > does not alter the actual bytes, just the interpretation of
  > them.
ZZ>

  Actually, there is no such rule.  A type cast is free to alter the
  value of an expression.  One of the more prevalent examples that
  breaks this "rule" is casting from pointer to integer and back again.
  There is no guarantee that the end result will equal the original
  pointer.

  It is not even guaranteed in Standard C that all integers can be cast
  to pointers without causing a program exception, or other undefined
  behaviour.

  So casting from a 0:32 pointer to a 16:16 pointer breaks no rule.

ZZ>
  >       If CSet does this it would almost surely mean that
  > the code you produced is non-portable, even not to another
  > compiler on the same platform !
ZZ>

  That's a bit of a non-issue, since thunking is by its very nature a
  platform specific thing.  It doesn't really make sense to worry about
  the portability of thunking.

  > JdeBP <
___
 X MegaMail 2.10 #0:DF> I repeat....  Huh ?

--- Maximus/2 2.02