Re: Pro C question
From: Mike Herring <mike-herring_at_worldnet.att.net>
Date: 1997/02/26
Message-ID: <01bc2403$49daa920$478493cf_at_micron>#1/1
Date: 1997/02/26
Message-ID: <01bc2403$49daa920$478493cf_at_micron>#1/1
Thanks for the reply. I finally realized that an instance of the oraca
structure (also called oraca) gets created
in the ORACA.H header file (which is #included indirecly via PROTO.H).
You have to make sure that only one
module compiles without #define ORACA_NONE in effect.
Chris Halioris <halioris_chris_nonlilly_at_lilly.com> wrote in article
<331329C9.4B0_at_lilly.com>...
> This may be a result of including ORACA.H in more than one of your
> modules. It has been a while but I think I remember something along
> those lines. If that is the case, make sure it is "included" in the main
> module and declared to be "external" in the others.
>
> Chris Halioris
>
Received on Wed Feb 26 1997 - 00:00:00 CET