 | | Re: legOS-0.2.1
|
|
Hi Jeffrey, that's an OS issue - your host system should define O_ASYNC. Some older systems define FASYNC instead, try that one. You can work around this more elegantly, too: #ifndef O_ASYNC #define O_ASYNC FASYNC #endif And hope for the best. (...) (25 years ago, 2-Nov-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx)
|
| |
| | Re: idiot's guide to programming the rcx
|
|
(...) The almost universal answer to the question "what is the best/easiest alternative programming language for the RCX" is three little letters: "NQC." If you are at all comfortable with programming in a "scripted" language like BASIC, then you (...) (25 years ago, 2-Nov-99, to lugnet.robotics.rcx)
|
| |
| | idiot's guide to programming the rcx
|
|
Can anyone tell me the EASIEST alternate programming language to use for the rcx. I mean, back in the days of BASIC, I was one of my state's top student programmers. But that was in the eighties. (25 years ago, 2-Nov-99, to lugnet.robotics.rcx)
|
| |
| | RS232 Communication
|
|
Has anyone read data into an RCX from an external device using an RS232 serial connection? The device I'd like to use might be spitting out data at about 16Hz. Any information at all will be a help. Cheers, Barry. (25 years ago, 1-Nov-99, to lugnet.robotics.rcx)
|
| |
| | Re: legOS-0.2.1
|
|
(...) ==bulk of message removed (...) I'm getting a compile error when building the dll utility - an undefined symbol 'O_ASYNC' forgive my ignorance but how do I fix this? Thanks in advance, -=RoboCoder=- (25 years ago, 1-Nov-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx)
|
| |
| | Re: Sharing variables and using expressions (was Re: NQC 2.0 and some math questions
|
|
Thanks, Dave! It will be good to have that in the manual, because it is a very confusing behavior that is difficult to track down. Variables take on values that are completely different from the values that the programmer is setting them to. Most (...) (25 years ago, 1-Nov-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Using ROBOLAB for FIRST LEGO League
|
|
(An earlier version of this email was initially posted on thursday october 28th to lugnet.robotics) SLIGHTLY UPDATED FROM LAST WEEK: If your kids are using ROBOLAB in this years FIRST LEGO League, I've written a replacement for pages 27-36 in the (...) (25 years ago, 1-Nov-99, to lugnet.robotics.rcx.robolab)
|
| |
| | RE: fast firmware downloader
|
|
(...) Great! I was using Borland C++ 3.0 because I happened to have the diskettes around. Remember when a C++ compiler fit on 5 (five) 3.5 diskettes? I have no problem with keeping the existing filename structure. It's readable, it serves the (...) (25 years ago, 1-Nov-99, to lugnet.robotics.rcx)
|
| |
| | Re: fast firmware downloader
|
|
(...) I agree with your reasoning. The compiler I have decided to use (Watcom C/C++ v.11 from Powersoft) will compile from the platform I am developing on (NT 4) to the desired executing platform (DOS) and will use long file names just fine. Other (...) (25 years ago, 1-Nov-99, to lugnet.robotics.rcx)
|
| |
| | Re: fast firmware downloader
|
|
(...) Sorry, but I'm going to be stubborn on this one. I abhor short (often cryptic) filenames. In the NQC source tree, almost every class is in its own file, which is of course named after the class. So in a sense, truncating the filenames is more (...) (25 years ago, 1-Nov-99, to lugnet.robotics.rcx)
|
