| |
Hi Ralph,
In lugnet.robotics.rcx.pbforth, Ralph Hempel writes:
> You generally allocate small stacks, so HAT could be modified to
> FORCE the data stack to start at the boundary if allocating it
> makes it across the 256 byte boundary...
Means that we will have to waste memory a lot...
Do you know how the standard LEGO firmware works? Does it allocate stack frame
for each task or may be it's not an issue at all?
> What about "4th" and standing man?
Yes, "4th" was always my favourite. Only question is how you can display it on
LCD? As I understood, our LCD with fixed matrix or not?!
> Something I wanted was to make a "vector" array that you can use
> to select one of 10 programs with the "PGM" key and then RUN them...
... and use the "VIEW" key to select a sensor and see it's raw values,
or use the "PGM" key to verify and control the state of active tasks...
Yes, that's could be really great.
BTW, when do you plan to make a new release?
Sergey
|
|
Message has 1 Reply:
 | | RE: Double echo
|
| (...) There are no "tasks really, just a big loop that executes a bunch of opcodes...I'm paraphrasing here. The memory waste issue isn't that big a deal. The average distance to a boundary is 128 bytes, right. Say we allocate a 32 element data stack (...) (25 years ago, 28-Oct-99, to lugnet.robotics.rcx.pbforth)
|
Message is in Reply To:
| | RE: Double echo
|
| (...) Yes, it should. The issue is that you never really know if the stack will blast through the 256 byte boundary, unless HAT checks it. You generally allocate small stacks, so HAT could be modified to FORCE the data stack to start at the boundary (...) (25 years ago, 28-Oct-99, to lugnet.robotics.rcx.pbforth)
|
5 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
