|
|
 | | RE: pbFORTH needs better uploading, docs
|
| Ben Jackson wrote.. (...) And Mark Terrabain replied... (...) I'm reluctant to take pbForth there because the RCX already compiles bytecodes and SAVE-SYSTEM sends them back to the host in Srecord format. Writing and testing a bytecode compiler for (...) (26 years ago, 9-Jan-00, to lugnet.robotics.rcx.pbforth)
| | | | | RE: pbFORTH needs better uploading, docs
|
| Ben, Thanks for emailing and feeding back some important issues for the rest of the Mindstorms pbForth community. I'll always welcome comments and respond as quickly as possible... Let me address each point, sorry about the quoting, but it's needed (...) (26 years ago, 9-Jan-00, to lugnet.robotics.rcx.pbforth)
| | | | | Re: pbFORTH needs better uploading, docs
|
| Well, I can rather agree on the uploading, but I don't find it quite as bad as you do. Not as good as NQC, but then NQC still has all the LEGO firmware limitations. As for the rest of your comments, I can only say that I managed to get the (...) (26 years ago, 9-Jan-00, to lugnet.robotics.rcx.pbforth)
| | | | | Re: pbFORTH needs better uploading, docs
|
| (...) This, IMO, is the biggest problem with pbForth as it exists. Although I have no idea why, Ralph seems reluctant to take pbForth to that point at this time. (And it makes even less sense to me when I think about the idea that most of this (...) (26 years ago, 8-Jan-00, to lugnet.robotics.rcx.pbforth)
| | | | | pbFORTH needs better uploading, docs
|
| So I've just been crawling over some broken glass, ERR, I mean, uploading pbFORTH text files to the RCX! It's hard to tell the difference! At the least, pbFORTH needs to: 1) accept \n, \r, \n\r or \r\n all as it does a single \r now. 2) have a mode (...) (26 years ago, 8-Jan-00, to lugnet.robotics.rcx.pbforth)
|
|
