 | | Re: NQC wishlist
|
|
A switch statment will be added pretty soon. The variable stuff is on hold for the moment. I'm holding off on the booleans until I work out a better strategy for variable allocation and code generation in general. Dave (...) for X-mas), (...) nested (...) (25 years ago, 3-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC wishlist
|
|
(...) Hi Dave, I'm using your wonderful tool since just a week now (bought my first RIS for X-mas), and I am already seriously running out of variables ... :-) So, I think your idea of variable types of less than 16 bits such as booles and shorts is (...) (25 years ago, 3-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: What should be in the next version of RcxCC
|
|
(...) Oops, that's right. I completely overlooked this. Thanks for the hint. So, my previous suggestion is quite pointless. Please ignore it. Sorry. Uwe (25 years ago, 3-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: What should be in the next version of RcxCC
|
|
You can also choose "show code/error listing" under the compile menu to get the variable assignments. Mike Uwe Denzer <Uwe.Denzer@munich.netsurf.de> wrote in message news:386F928E.984386...surf.de... (...) like to (...) up in (...) and I'd (...) (...) (25 years ago, 3-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: What should be in the next version of RcxCC
|
|
(...) After spending another two nights with NQC & RcxCC (:-), another wish came up in my mind quite clearly: I use the "Watching the RCX" tool window quite frequently for debugging, and I'd find it great if it could display the *names* of the (...) (25 years ago, 2-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: What should be in the next version of RcxCC
|
|
How about a more generalized interface to the pbForth system. Although Ralph Hempel believes this to be unnecessary, I find the RcxCC interface quite appealing. Harald Striepe (25 years ago, 2-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: What should be in the next version of RcxCC
|
|
(...) Thanks, Mark, for providing this wonderful environment. I would like to echo a previous request for remembering last-used source-file paths between sessions. Also, how about letting RccxCC "host" alternative line editors? (25 years ago, 1-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: What should be in the next version of RcxCC
|
|
(...) First of all, thanks a lot for making RcxCC. I'm a newbie (owning my RIS since X-mas), but I already love NQC and RcxCC. There's just one little feature that I missed: remembering the last-used path for source files between sessions. Ah yes, (...) (25 years ago, 1-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | RcxCC with NQC 2.1
|
|
Hi, does anybody know why RcxCC can't spawn NQC 2.1 b1? Is there a trick to do it (other than waiting for the next version of RcxCC)? Uwe (25 years ago, 1-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Can't open serial port in Linux
|
|
(...) Currently there isn't any notion of an "error code" from the serial port class - opening the serial port just returns true/fals. I'm wary of adding error codes here because they'd need to be added in a portable manner (and across the Unix, (...) (25 years ago, 30-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Can't open serial port in Linux
|
|
Hi. I just got through fixing a similar problem with my linux box (the fix involved a lot of tedious changing IRQ's in the BIOS, with a lot of tedious rebooting in between). Beyond Dave's good advice, you might want to check out the linux serial (...) (25 years ago, 30-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Can't open serial port in Linux
|
|
Check the permissions on /dev/ttyS1. I think the default is for it to be locked down to superuser only. If this is the case, then running nqc from a normal user account would cause the error you got. You'll need read/write rights to /dev/ttyS1 in (...) (25 years ago, 29-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Can't open serial port in Linux
|
|
I'm having some troubles downloading to the RCX in Linux, I have RXC_PORT set to /dev/ttyS1, which is the correct serial port, and then I run nqc and get: [brian@magic bin]$ ./nqc -d ../test.nqc Downloading Program:error Could not open serial port (...) (25 years ago, 29-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | firmware upload with NQC...
|
|
first off, i'm using NQC with Linux. when i try to upload the firmware image from the MindStorms CD-ROM, i get the following: [kjs@localhost nqc_lnx_2_0_2]# ./nqc -firmware ../FIRM0309.LGO Downloading firmware:... Problem talking to IR device the (...) (25 years ago, 27-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Roboarm.nqh
|
|
(...) I'm glad you're enjoying the book. Not including more information about where to put include files was definitely an oversight - I'll update the book's web pages when I get a chance. Dave (25 years ago, 22-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Roboarm.nqh
|
|
I was using the RcxCC program. I put the nqh file in the RcxCC directory and everything worked fine. Thanks for the information. By the way, I am really enjoying your book. I hope everyone gets a chance to read and use it. -- Bob Fay (...) (25 years ago, 22-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Roboarm.nqh
|
|
(...) The idea behind including files is that it allows a common set of definitions and/or functions to be shared by multiple programs. NQC by default searches the current directory for any include files. It is also possible to specify a search path (...) (25 years ago, 22-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Roboarm.nqh
|
|
I am working my way through Dave Baums' Mindstorm book and I have lost my way regarding the #include command. The roboarm1.nqc program calls for roboarm.nqh to be included. The program will not compile because it "cannot open roboarm.nqh". Some (...) (25 years ago, 22-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Can't compile test.nqc
|
|
(...) There is very little difference in the compiler itself between 1.0 mode and normal mode. Most of the changes are due to a new API file that is included (rcx_nqh.h). If something went wrong with building this file, that may cause a crash. To (...) (25 years ago, 20-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Can't compile test.nqc
|
|
Hi, I have been trying to compile NQC (2.0.2) with the watcom compiler under QNX and succeded partialy. I can now compile the test.nqc from version 1.3 in backward compatibility mode (bin/nqc -1 testv1.nqc). But I can't compile the new test.nqc (...) (25 years ago, 20-Dec-99, to lugnet.robotics.rcx.nqc)
|
