On Tue, 30 Aug 2011 12:07:29 +0300 Kustaa Nyholm <kustaa.nyh...@planmeca.com> wrote:
> On 8/30/11 01:23, "Mario" <marbar...@gmail.com> wrote: > > >Just as described at section 3.6. > >I have managed to make it work partially, for example, I can decide > >the address in the RAM of variables only when they are globally > >defined. > > How could you define the address of a local variable? Conceptually > it is in the stack and the address varies from invocation to > invocation. The compiler can itself fix the scenarios to make the variables appear in such address when needed. If the compiler cannot do that, it should at least let me know that that rule within a local function context, makes no sense. ------------------------------------------------------------------------------ Why Cloud-Based Security and Archiving Make Sense Osterman Research conducted this study that outlines how and why cloud computing security and archiving is rapidly being adopted across the IT space for its ease of implementation, lower cost, and increased reliability. Learn more. http://www.accelacomm.com/jaw/sfnl/114/51425301/ _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
