Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!uw-beaver!zephyr.ens.tek.com!tektronix!percy!data!kend
From: kend@data.UUCP (Ken Dickey)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Storing far pointers in windows programs.
Message-ID: <493@data.UUCP>
Date: 15 May 91 23:09:53 GMT
References: <6150@eastapps.East.Sun.COM>
Distribution: na
Organization: Microcosm, Beaverton, OR
Lines: 16



For that matter, what about far pointers on the App stack when a
low-level routine in a DLL "Blocks" waiting for a message {via
GetMessage() or PeekMessage()}?  

It appears from the SDK documents that Windows locks the application's
data segment when it gives it the CPU.  If the DS is unlocked in a
DLL's GetMessage() call, and far pointers are required to pass data
through DLLs, then there is no way to safely "block" within a DLL to
present a synchronous interface to its caller!

Does anyone know more about this?

Thanks,
-Ken Dickey					kend@data.uucp