🚀 go-pugleaf

The macro STRICT alters how the Windows header files are expanded.  It was
added to support later versions of Windows.  If you your code is also
intended to be compiled for pre-1992 Windows < 3.0 came out then do not
define STRICT.

The major effect is of STRICT is to cause the Windows header files to be
expaned with function prototypes that have argument lists.  Unlike C, C++
requires function prototypes so if STRICT is not defined you will see more
casts in the code to subvert compiler checks.

.  Ed

> Martin Golm wrote in message
> news:40167C39.252A09F9@gmx.de...
>
> When writing a WinAPI-only application, should I define
> STRICT or not? What is the difference between defining
> STRICT and not defining it? OWL applications have STRICT
> defined as default (but that's probably just to match the
> definitions of ::WndProc and TWindow::WndProc).
> Maybe some of the older Windows programmers can shed
> a bit of light to me.