 | | Re: NQC default output file
|
|
(...) I don't want the outfile to go where the executable is -- I want it to go to the current working directory. So nqc goes in /usr/local/bin, and I can run it from "binaries" directory on source files that might be located elsewhere (the test.nqc (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC default output file
|
|
I don't think it's nonintuitive. I think it makes sense to have the output go to the same directory as the input. That way you can have a directory set up for the executable with only read/execute permissions, and yet have all of your source & (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC default output file
|
|
I was checking to see if NQC already does have an option to spit bytecodes to stdout (-L would work, if rcxcomm would understand the format) and I came across something that seems nonintuitive to me. The default output file is "named the same as the (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.1 b2 in beta test
|
|
(...) If this is done, the compiler should have an option to spit out compiled bytecode on stdout, and the rcxcomm program should have a matching option to accept bytecodes on stdin and send them to the rcx. And then there should be a wrapper that (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | More details : "Exploration Mars" and "Ultimate Accessory Set" for the RCX available in march ?
|
|
Hi again all, Thanks to Jesper Kjaer, here is posted more information and detailled pictures for these to sets. Please see : (URL) large pictures posted). About Exploration Mars (#9736) : - Unfortunately, this set doesn't seems to contain a cam... - (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx)
|
| |
| | 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)
|
