Jonathan de Boyne Pollard wrote in a message to Wim Veldhuis:

  >       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 !

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

Not completely I think. Noticing the lack of compiling speed with CSet++, I
thought it might be handy to compile with Borland first (when I program a
real thing under OS/2) and finally in CSet for the execution speed of the
program. If BC does not do this automatically, I would get errors I did not
expect. OTOH, I am not sure if it would gain much time during development
and I doubt it I will use a 16-bit DLL, so it is indeed a bit of a
non-issue 

But thanxs for the correction of my incorrect vision of typecast results.

mvg/wr
  
--- timEd/2 1.01.g3+