Subject:
|
Re: maximum number of variables in RCX2 ?
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Wed, 20 Feb 2002 13:47:41 GMT
|
Viewed:
|
3486 times
|
| |
|
|
In lugnet.robotics.rcx.nqc, John Guerquin writes:
> The reason I ask this question, is that my understanding of local variables
> is that space is allocated only when the function has been called. Once the
> function is complete, the memory that was used to store those local
> variables is returned back to the ‘memory pool’.
Remember that the RCX has no stack or heap. This means that, effectively,
there is no memory pool from which to allocate things. Here, 'local' means
belonging to the current task not the current function, and the number of
tasks is fixed (at 10). There is no dynamic memory allocation.
The same limitation means that functions cannot call each other, because
there is no stack on which to store the return address. The main advantage
of LegOS is that it has a stack and a heap, but it is much more complicated
to use.
Barney.
|
|
Message is in Reply To:
 | | maximum number of variables in RCX2 ?
|
| When using the RCX2 target, the NQC manual (Section 2.2.4) states that 32 global variables, and 16 local variables (per task) are allowed. Does this mean that the whole program can only have 48 variables total when using only one task, ie. "main" , (...) (23 years ago, 20-Feb-02, to lugnet.robotics.rcx.nqc)
|
5 Messages in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
