|
| | Re: Storing Data
|
| (...) It was suggested by some of my 'c++' co-workers that this was the case (shared memory was available). However, I don't deal with that in my Visual Basic world. They also suggested there were 'unused' memory blocks in LegOS where data could be (...) (23 years ago, 21-Dec-01, to lugnet.robotics.rcx.legos)
| | | | Re: Storing Data
|
| (...) As there is no memory management, any memory not on the stack is by definition shared between any threads. Concurrency control is up to you however. John A. Tamplin jat@jaet.org 770/436-5387 HOME 4116 Manson Ave 770/431-9459 FAX Smyrna, GA (...) (23 years ago, 21-Dec-01, to lugnet.robotics.rcx.legos)
| | | | Re: Storing Data
|
| (...) What you request is shared memory and shared memory is not a part of legOS. My way to simulate shared mem is to put the two (or more) tasks into one legOS program. Each task is started as a thread by an execi() call, triggered by the user via (...) (23 years ago, 21-Dec-01, to lugnet.robotics.rcx.legos)
| | | | LNP: host address
|
| Is there a reason to "hardcode" the host address using a define (LNP_HOSTADDR)? Things would be easier for me if I could change the address at run time (when calling lnp_init). Is it safe to replace the defines by a variable? Eric (23 years ago, 21-Dec-01, to lugnet.robotics.rcx.legos)
| | | | Proximity
|
| Next question: Does any one have a proximity routne (code) I can review (steal) using LegOS, a light sensor, and the IR port? I've used the NQC stuff, but now I've moved up to LegOS. I haven't been able to find the right commands for the IR port. (...) (23 years ago, 20-Dec-01, to lugnet.robotics.rcx.legos)
| |