|
|
 | | Re: pbForth vs RCX 1.0
|
| Thanks, Just to make sure, let's take an example. Let's say that I have two RCX, named A and B. What if the program in RCX B is waiting for a character on the instruction KEY and RCX A sends a character, let's say '5' (ASCII 52) with 52 EMIT ? That (...) (22 years ago, 27-Jun-02, to lugnet.robotics.rcx.pbforth)
| | | | | Re: pbForth vs RCX 1.0
|
| "Mario Beaulieu" <mariobeaulieu@videotron.ca> writes... (...) Yes. I run pbForth on RCX 1.0, 1.5 and 2.0. No differences. (...) No, to my knowledge. In pbForth the IR port is entirely devoted to communication between the brick and the terminal. (...) (22 years ago, 27-Jun-02, to lugnet.robotics.rcx.pbforth)
| | | | | pbForth vs RCX 1.0
|
| Hi, Is pbForth fully compatible with RCX 1.0? Can RCX 2.0 communicate with RCX 1.0 in pbForth (using IR ports)? Thanks Mario (22 years ago, 26-Jun-02, to lugnet.robotics.rcx.pbforth)
| | | | | pbForth questions
|
| The output of my compiler typically looks like: \ Begin code sample FORTH CODE ... ... : ENTRYPOINT ... ; 0 ENTRYPOINT \ End code sample Or, in other words, I'm currently (and this isn't permanent) not allowing programs to be compiled that do not (...) (22 years ago, 26-Jun-02, to lugnet.robotics.rcx.pbforth)
| | | | | RE: Displaying info while debugging
|
| Mario (and all other pbForth users - both of you :-) I'm very happy to include ANY contributions that you may have in the source archive. Even if I don't update the actual core, I still add useful scripts to the distribution all the time. Any (...) (22 years ago, 17-Jun-02, to lugnet.robotics.rcx.pbforth)
|
|
