 | | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
Mark Riley wrote: [snip] (...) This is easy enough to implement (1 or 2 lines), but raises the question: Should these memory strategies be included with BrickOS (with a config.h flag to control it)? I am sure the educators would rather leave that (...) (22 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Global Objects was Strange RCX startup issues
|
|
Understood. In this case, I am thinking that the option should be ON by default; such that a new, less experienced user would not encounter a problem; but an experienced user could turn the option off. // Joe (...) (22 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Global Objects was Strange RCX startup issues
|
|
(...) But, it perhaps should default to being enabled as this deficiency has caused some confusion in the past. Great work, Joe! Mark (22 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Global Objects was Strange RCX startup issues
|
|
(...) I opt for option. Not much may be to much in some cases. And I don't want to program in c++ anyway. Regards, Michael (22 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Global Objects was Strange RCX startup issues
|
|
(...) [snipped] (...) I simply added ctor_size and dtor_size to the *image*, *lx* and *program* structures. This allows the program manager to calc the start and end of these segments. (...) It wasn't as hard as I had thought. I have the fix (...) (22 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos)
|
