🚀 go-pugleaf

In article <1992Jul24.212525.26422@ultb.isc.rit.edu> sxl2259@ritvax.isc.rit.edu writes:
>
>Does anyone know about how to port the Windows programs to MetaWare compiler
>for 32-bit environment (of course, still running under Windows 16-bit
>environemnt). I have trouble to use the GlobalAlloc & GlobalLock. Because
>the MetaWare include a NEW windows.h that declare FAR as "". (nothing)
>
>How to change my program without pain? By the way, no matter what the Local
>or Globle memory API used, I always got a compiler waring like that:
>
>"far pointer address truncated to near pointer"
>
>Why? especially in GlobalLock and LocalLock!?
>
>
>Any suggestion will be very appreciated, 
>
>
>SHen-wei
>

The MetaWare ADK converts the results of GlobalLock and LocalLock to
32-bit Far pointers. What you really want to do is switch to malloc
if you're writing C or new if you're writing C++.

Note that near 32-bit pointers (as returned by malloc or new) give you
the full speed you wanted when you went to 32-bit integers to begin with.
Far 32-bit pointers are just as slow as far 16-bit pointers.

-- Martin Heller
Programming Columnist, WINDOWS Magazine