|
|
 | | RE: Multiplexing 4 touch sensors on an RCX input port
|
| (...) Ian, Great to see that you are having success with pbForth! I have a couple of questoins: 1. Which version are you using? 2. Are there any features you REALLY wish were available? 3. Do you have any stories or code to share? Ralph ---...--- (...) (21 years ago, 10-Sep-03, to lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
| | | | | RE: leJOS & BricxCC news
|
| (...) OK, I've looked at your wish list and have the following comments with respect to how I see the pbForth implementation of DCC. 1. How important is it to have more than one port with DCC capabilities. The reason I'm asking is that it "would be (...) (21 years ago, 7-Sep-03, to lugnet.robotics.rcx, lugnet.trains, lugnet.robotics.rcx.pbforth)
| | | | | Re: leJOS & BricxCC news
|
| (...) Hmmm. I was seriously considering writing a leJOS package to support the LDCC IR Protocol. (Here's why: (URL) ) What capabilities were you going to add? Depending on your timeline, you might convince me to try FORTH. (21 years ago, 7-Sep-03, to lugnet.robotics.rcx.java, lugnet.robotics.rcx, lugnet.trains, lugnet.robotics.rcx.pbforth)
| | | | | RE: pbForth & ROLL
|
| (...) John, As always, it depends. ROLL can sometimes be recovered gracefully, but not always. If you ROLL more than the stack depth, you'll shift some RAM that you probably don't want to shift - like the pbForth image itself. In that case, there's (...) (21 years ago, 6-Sep-03, to lugnet.robotics.rcx.pbforth)
| | | | | pbForth & ROLL
|
| (...) While testing my console the other day I kept getting pbForth to hang (or so it appeared). It turns out I was passing ROLL a number that caused it to do bad things. I'm wondering whether it should error out with "aborted stack underflow" or (...) (21 years ago, 6-Sep-03, to lugnet.robotics.rcx.pbforth)
|
|
