DL>
  > the stack for the function call. I am assuming that the problem is that the
  > stack pointer handed to me by the 16-bit NSFSearch function calling my 32-b
  > "action_routine" needs to be thunked before I can use it.
I haven't the
  > slightest idea how to make sure my stack pointer gets thunked when the 16-b
  > code calls my 32-bit routine... Would anyone who knows how
  > please help me out?
DL>

  There are basically two directions for thunking.

  The first is 32->16, where 32-bit code is calling 16-bit libraries,
  such as your Lotus Notes stuff.  This is done by declaring the 16-bit
  API using _Far16 and so forth, and CSet++ will insert pointer and
  stack conversion code in the 32-bit code that calls the function for
  you. As you said, you seem to have this down pat.

  The second is 16->32, and is usually encountered where you need to
  pass a callback function to a 16-bit library.  This is more complex,
  because obviously the 16-bit code will be expecting to call a 16-bit
  function on a 16-bit stack using 16-bit pointers.  Functions written
  for the 32-bit world won't work.

  What you need to do is define your callback function as a 16-bit
  *callable* function.  You do this in the same way as you declare a
  16-bit *called* function, by using _Far16 and friends.  The only
  difference is where the thunking code goes.  This time it goes in the
  callee, not the caller.

  For example, this function is callable by 16-bit code

      void _Far16 _Cdecl callback ( short a, short b ) {}

  What happens now is that CSet++ at the start of the body of the
  function generates all of the code to convert from a 16-bit stack to a
  32-bit stack, and at the end of the function generates the code to go
  back again.  To the 16-bit world, this looks just like a 16-bit
  function, but the body of the function runs in the normal 32-bit
  world.

  This is all covered in the CSet++ manual, by the way.

  > JdeBP <
___
 X MegaMail 2.10 #0:
--- Maximus/2 2.01wb