On Wed, Jun 23, 2010 at 10:52 AM, Michael Schippling wrote:
> Oh, I see. I don't need two header files to declare and define
> the variable. Since everything is conglomerated into one app.c
>
correct.
> file before real compilation occurs, all I need is the definition
> file that allocates the
Oh, I see. I don't need two header files to declare and define
the variable. Since everything is conglomerated into one app.c
file before real compilation occurs, all I need is the definition
file that allocates the space and assigns it a name.
Don't need the #ifndef __HEADER_H__ thing either...
On Tue, Jun 22, 2010 at 9:30 AM, Michael Schippling wrote:
> Err. Uh...Wot?
>
> That second paragraph appears to have fairly standard English
> syntax and grammar but makes absolutely no sense to me.
> Are you using an auto-reply generator?
>
sorry, forgot to turn off the AI :-)
The points I wa
Err. Uh...Wot?
That second paragraph appears to have fairly standard English
syntax and grammar but makes absolutely no sense to me.
Are you using an auto-reply generator?
The points I was trying to make are,
A) yes, one can declare and use global variables;
B) this has to be done in header files
what you are running into is the order the files are scanned.
If you do the .h business then you include that and it doesn't matter
because your
include file is protected against being included twice.
On Mon, Jun 21, 2010 at 12:22 PM, Michael Schippling wrote:
> In re: creating real global varia
In re: creating real global variables under NESCC.
WOW! I think you've got it. Almost anyway...
I'm pretty sure I tried the (sort of obvious) method of
[declar,defin}ing a variable outside of the
module{}implementation{} block in a .nc file, ala:
includes RoboMsg;
static int foolish;
