Hi Reed -

You're right that nothing defined it anywhere, but something sticks in my
mind that says the define is not used entirely for win16 (though it should
be). I may be remembering something about building classic (or maybe I am
hallucinating).

-Mark

----- Original Message -----
From: reed mideke <rfm@...>
To: <IB-Architect@egroups.com>
Sent: Tuesday, August 01, 2000 2:27 PM
Subject: Re: [IB-Architect] Win16


> Hi Mark!
>
> willaby@... wrote:
> >
> > Hi -
> >
> > All references to HARBOR_MERGE can be safely removed. These were just
> > placeholders and there was a 'procedure' which we tried to follow when
> > checking in modules.
> >
> > As for WINDOWS_ONLY, be careful. In 90% of the code, removing this
define
> > is OK, however there are some cases (they escape me at the moment) where
> > WINDOWS_ONLY is used in place of WIN_NT (which is generic for all
Windows
> > platforms).
>
> Are you sure ? I seem to remember SUPERCLIENT being misused, but
> I can't imagine where WINDOWS_ONLY was abused that way in the core
> product. I know that the makefiles >never< define it. So it would have
> to be something literally defined in the file that needed it, or
> something like
> #define WINDOWS_ONLY
> #include "some_lame_header.h"
> #undef WINDOWS_ONLY
>
> The other possiblity is that it was done in the old server manager or
> wisql code, but these aren't included in the source release.
>
> >
> > -Mark (former IB engineer)
> >
> [...]
> --
> Reed Mideke rfm(at)cruzers.com
> If that doesn't work: rfm(at)portalofevil.com
>
>
>
> To unsubscribe from this group, send an email to:
> IB-Architect-unsubscribe@onelist.com
>
>
>