|
From: | Steve Franks |
Subject: | Re: [avr-gcc-list] eeprom issue |
Date: | Fri, 11 May 2007 00:23:43 -0700 |
On 5/10/07, Gavin Jackson <address@hidden> wrote:
Declaring the RAM variable as static would restrict it's scope to the module (read .c file) in which it's found according to the C standard. If one of your .c files was changing the variable and you could see those changes from the other .c file with both variables declared as static, then you have certainly found a bug, but one that would have been found in the early days of the compiler. There must be some other explanation for what you've observer.
Ah. The "ram" variable may have been a static class member, in which case there really is only one, no? Keyword salad, anyone? Steve
[Prev in Thread] | Current Thread | [Next in Thread] |