 | | Re: local variables
|
|
(...) I think you're confusing the issue a little bit. LegOS only initializes GLOBAL variables when the program is loaded. So, for example, a global variable declared like: int foo = 4; Will only be initialized to 4 when the program is loaded. If (...) (24 years ago, 17-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | local variables
|
|
Hi! I read that legOS only declared varibles the first time the program is run. Does this mean I cannot use local variables. I have loops in different functions using 'i' as looping variable, which is locally declared. Should I avoid this? Tobias (24 years ago, 16-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: lnp communication question
|
|
(...) So the length-argument tells lnp_integrity_write how many bytes to send? Doesn't that mean that it would be possible to send an array consisting of many integers, for example? How would this be done? (...) We plan to build a six-legged lego (...) (24 years ago, 16-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | winlegos compiler problem
|
|
I am trying out the lnp functionality with addressing and such, and of course I had to recompile the legos kernel. That, in itself, seemed to go without a hitch, but when I later tried to compile one of the demo programs, this is what I got. djecho (...) (24 years ago, 16-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: lnp communication question
|
|
Hello Tobias, (...) Why do you think there's only 1 byte that can be sent? If your data buffer is longer, bytes are sent one-by-one serially in a packet... (...) look into lnp.c and you will see that both lnp_integrity_xxx and lnp_addressing_xxx are (...) (24 years ago, 15-May-00, to lugnet.robotics.rcx.legos)
|
