WinCon.DLL; nested structures

From: Mike Ghan <mikeg_at_logix-controls.com>
Date: Mon, 11 Dec 2000 12:46:23 -0800

> This is also a valid conclusion. I very often use PAD or HERE as that
> temporary buffer. In a callback, which is the only place one would
need
> to reference this structure, PAD and HERE are both valid and
guaranteed
> *not* to be unique and free for use.

> Rick

Rick, am I missing something? My understanding is PAD and HERE are both
created on and exist on the Windows message stack frame. This *would*
make them unique for every message *and* transient - once the message
exits, the stack frame is destroyed. Is this correct?

Mike
Received on Mon Dec 11 2000 - 13:01:10 PST


Subscribe to our e-mail list service. It's free for all SwiftForth and SwiftX users!

This archive was generated 09-Feb-2012. Archive updated nightly.