 | | LegOS Firmware Problem
|
|
I'm using LegOS 0.2.3 under a Slackware 7 Linux install and everything seemed to work perfectly to begin with. I've recently tried altering the kernel a bit -- everything compiled fine as far as I could tell. When I tried to use firmdl3 to download (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.legos)
|
| |
| | RE: TpForth Project ?
|
|
(...) The basic problem, Mark, is time. I just don't have the time to properly support a compiler for three platforms. I can barely keep up with the demands pbForth makes of my spare time. I write strict ANSI-C all day long, and pbForth is a bit of (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: TpForth Project ?
|
|
(...) The basic problem, Mark, is time. I just don't have the time to properly support a compiler for three platforms. I can barely keep up with the demands pbForth makes of my spare time. I write strict ANSI-C all day long, and pbForth is a bit of (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: NQC 2.1 b2 in beta test
|
|
(...) I think NQC should be strictly a compiler. It seems like it would be more manageable for both developers and users if the RCX communication pieces were in a separate executable. This change should make NQC completely portable (if there is such (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.1 b2 in beta test
|
|
(...) The beta does not seem to work with RcxCC. All it does is display the parameters for NQC and then exits. No compile. --- DonC donc@cccd.edu (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
