|
|
 | | Re: WORDLIST
|
| (...) Ah, I didn't know of that. (...) BTW, I'd like to suggest (to Ralph, not you) that the pbForth scripts included in the release should use .4th or .fth or something a bit more distinctive. They're now .txt, so BricxCC does not recognize them. (...) (21 years ago, 17-Jan-04, to lugnet.robotics.rcx.pbforth)
| | | | | Re: WORDLIST
|
| (...) snip A while ago, I started to work on a few words that I find useful,including WORD and SEE. I still have to finish them, but what would help is to know the structure of the dictionary (starting with the execution address obtained by tick (...) (21 years ago, 17-Jan-04, to lugnet.robotics.rcx.pbforth)
| | | | | Re: WORDLIST
|
| (...) The pbForth documentation which is included with the latest release of BricxCC indicates which of the ANS FORTH words are supported by pbForth. If you open a forth document (one with an extension which BricxCC recognizes as a forth document) (...) (21 years ago, 16-Jan-04, to lugnet.robotics.rcx.pbforth)
| | | | | RE: WORDLIST
|
| Good questions Juanma! If WORDS is very important for you, I can write up a quick tutorial on how to do that. I'm pretty sure all of the CORE or REQUIRED ANS Forth words are supported. I'll need to update my build script to output a list of the (...) (21 years ago, 16-Jan-04, to lugnet.robotics.rcx.pbforth)
| | | | | WORDLIST
|
| Is there any way in pbForth to list the currently defined words, à la WORDS? Also, is there any document that list which ANS FORTH words are supported by pbForth (other than reading the source, I mean)? Thanks. (21 years ago, 16-Jan-04, to lugnet.robotics.rcx.pbforth)
| | | | | RE: Problem with rcxTcl.exe and the USB IR tower
|
| (...) I'll check this out on a system that has absolutely no Tcl support, but as you might expect - it works fine here :-) (...) I'm sure John Hansen would appreciate any feedback on BricxCC - even if it'a a problem report. (...) That's the spirit! (...) (21 years ago, 15-Jan-04, to lugnet.robotics.rcx.pbforth)
| | | | | Re: NQC's future
|
| (...) ;o) ... but why not ? (...) You're right, I should try pbForth, actually I intend to do that for a while but never jumped in. In the late 80's, I was involved in a point of sales terminal project that was programmed with a preemptive (...) (21 years ago, 9-Jan-04, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics, lugnet.robotics.rcx.pbforth)
| | | | | Q for Ralph
|
| Why, exactly, does pbForth use a terminal emulator for the PC to talk to the RCX? Although I admit I find it an interesting concept (it's got a certain nostalgic appeal, at least for me), the design seems to encourage leaving the RCX on for extended (...) (21 years ago, 9-Jan-04, to lugnet.robotics.rcx.pbforth)
| | | | | IR problems
|
| Hi, I was having some problems in a program I'm writing in PbForth and it seems that it could be related to the way I communicate thru IR. I use the Lego remote control. I joined the following code to demonstrate. I use the word 'getHeader' from (...) (21 years ago, 9-Jan-04, to lugnet.robotics.rcx.pbforth)
| | | | | RE: NQC's future
|
| (...) Ha Ha, very funny :-) Seriously, Philippe, why not give pbForth a try? I know that NQC works great on both the Spybots and the RCX, and even Cybermaster. But if you're looking for speed, higher precision, lots of variables and generally more (...) (21 years ago, 8-Jan-04, to lugnet.robotics.rcx.nqc, lugnet.robotics.spybotics, lugnet.robotics.rcx.pbforth)
|
|
