MS>
  > here's a long full version of dll-initterm for vacpp for
  > OS/2 and Windows from IBM:
MS>

  Interesting.  I disagree with their putting user code in _DLL_InitTerm,
  however.  User code is better off driven by the constructor and
  destructor of a class instance with static storage duration.  That way,
  it is more exception-proof, and the programmer is assured that at the
  time that his initialisation/termination code is run, the C++ RTL is
  fully available.

  In their code that you quoted, placing initialisation code at the point
  of the "user code goes here" comments would restrict the programmer to
  not using any C++ RTL functions during DLL initialisation, since the
  call to _CRT_Init would not have yet occurred at that point.

  I suppose, in a way, mine is a minimalist approach.  DLL initialisation
  and termination is such a compiler-dependent thing that I advocate
  putting as little user code as possible in the actual _DLL_InitTerm/
  _dllmain/__dll_initialize function, and using more "conventional"
  mechanisms (like constructors and destructors) for user initialisation
  and termination.

  Having a class instance that represents the DLL can be a handy thing to
  have around, anyway ... (-:

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