 | | Interactive C Primitives —Nick Taylor
|
| | | There are several IC primitives for which I cannot find documentation nor source, such as: poke, peek, pokeword, peekword, bit_set, bit_clear These six are relatively simple to figure out by context and familiarity with other languages, but I find (...) (26 years ago, 7-Feb-99, to lugnet.robotics.handyboard)
|
| | | |
| | | | | Re: Interactive C Primitives —Nick Taylor
|
| | | | | My apologies for having posted this question. After re-reading the HB Tech Manual for the umpteenth time, para. 5.10 suddenly appeared out of nowhere! *Nick hangs his head in shame* - - - Nick - - - (...) (26 years ago, 7-Feb-99, to lugnet.robotics.handyboard)
|
| | | | | |
| | | | | Re: Interactive C Primitives —Fred G. Martin
|
| | | | these are documented in sec 5.10 of the hb tech ref. the larger issue is knowing the places you are supposed to peek and poke. some of these are hardware specific (e.g, motor port); others are software based/defined in the pcode implementation (...) (26 years ago, 7-Feb-99, to lugnet.robotics.handyboard)
|
| | | | |
| | | | | | Re: Interactive C Primitives —Richard Drushel
|
| | | | [Fred G. Martin] spake unto the ether: (...) Security through obscurity is always a bad idea :-) I can agree that software data structures are not public, but all the hardware stuff should be documented, since it's not likely to move around. *Rich* (26 years ago, 7-Feb-99, to lugnet.robotics.handyboard)
|
| | | | |
