🚀 go-pugleaf

I am having difficulty getting an application object library to work
without generating segment violation errors under OS/2 V1.3 using the
Microsoft C6 compiler.

The modules which make up the library are being compiled using the
/MT /AL /Aw /G2 /Gc switches because they are ultimately destined to be
part of a DLL (they are not currently).

I am having some difficulty deciding when to use the _loadds attribute
on the individual functions, and the absence of this attribute on some
of the components of the library seems to be the primary cause of the
problem.

All of the problems (so far) appear when one module passes stack variables
by reference to another module. For some reason the receiving module cannot
reference the caller's data. It even happens when private modules (those not
referenced outside the DLL) in a separate thread wake up on a timer and pass
stack variables by reference to another function (which then blows up). The
offending private modules have static data.

These are my questions:

	1 - When do you use the _loadds attribute, and when do you not
	    have to?

	2 - Can the private parts of the library, that is those functions
	    which cannot be called outside the library, be compiled using
	    a standard model (ie: /MT /AL), while only the exported sections
	    are compiled using /ALw?

	3 - If the answer to (2) is no, then does that mean that even some
 	    private modules must have the _loadds attribute?

	4 - Does the main() need any special attributes if it is compiled
	    using /ALw?

	5 - Why can't the Microsoft C "Advanced" Programming Techniques
	    manual answer some of these stupid questions?