didier wrote:
> Reusing the space occupied by a global variable would be very
> bad indeed. Is it what is happening here?
yes. sorry i wasn't clear in my earliest mail.
it happens because of the way sdcc treats "char at 0xf000 foo;".
it apparently doesn't actually enter "foo" into the symbol
Subject: Re: [Sdcc-user] laying out memory
Didier,
In this regard the keyword static has the same effect as making the variable
global. I guess Paul already made his variables global.
-
This SF.Net email is sponsored by the
at
> are overlaid are truly independent. It reduces RAM usage sometimes
> dramatically.
>
> Didier
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED]
> Sent: Monday, August 18, 2008 1:08 PM
> To
essage-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Monday, August 18, 2008 1:08 PM
To: sdcc-user@lists.sourceforge.net
Subject: Re: [Sdcc-user] laying out memory
didier wrote:
> Would'nt the "static" keyword take care of that?
i'
didier wrote:
> Would'nt the "static" keyword take care of that?
i'm not sure how that would help.
>
> Is it that you want to know where the variable resides, or
> simply to make sure the memory space is not overlaid with
> another variable?
well, it's never my intention to inadvertently u
Would'nt the "static" keyword take care of that?
Is it that you want to know where the variable resides, or simply to make sure
the memory space is not overlaid with another variable?
Didier
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECT
