 | | Emulating arrays in NQC
|
|
Hi all! as I promised earlier, I am posting the code I've written to emulate arrays. I tried to make it general, but it's difficult to do without compiler support. Right now it implements a 32 items array of 4 bit variables. It can be quite easily (...) (25 years ago, 6-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC wishlist
|
|
(...) I think 1 and 2 are the ones that would be really needed. 2 would be useful in writing macros to emulate arrays or "small" variables. But maybe there will be support for that in the compiler... cheers /Vlad (25 years ago, 6-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC beta test release policy
|
|
As this is my first post to this newsgroup, I thought I'd start by saying how wonderful I think nqc is etc. I got the RIS 1.5 for xmas and had nqc up and running in no time on my linux system. As well as being an excellent language and bytecode (...) (25 years ago, 6-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC wishlist
|
|
(...) That would still be handy. Just the other night I was readying some NQC for distribution and I had: #define FOO_SENSOR SENSOR_2 and what I wanted to do was (beyond the user configurable part): #define DISPLAY_FOO DISPLAY_ ## FOO_SENSOR so I (...) (25 years ago, 6-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC wishlist
|
|
Dave, So far, I've lived without ##, and I'm quite sure I can live without 4) and 5). And can't 3) be replaced in many cases by arithmetic? In my brief stint programming "lego assembler" for the Scout, (Assembler! I'm embarrassed to admit how far (...) (25 years ago, 6-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC wishlist
|
|
(...) I took a good look at the preprocessor code, and it shouldn't be too hard to implement ## aside from the problem of recovering original token text. Adding support for remembering the original token text is easy to do if you're willing to be a (...) (25 years ago, 6-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC wishlist
|
|
(...) If I were to implement it, I probably wouldn't add a second pass. The real obstacle at present is that the literal text for a token cannot always be recovered after it leaves the lexer. For example, '01' and '1' both leave the lexer as an (...) (25 years ago, 6-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: What should be in the next version of RcxCC
|
|
1: a default template file, so that standard includes and defines, a main task and other things that tend to be used in all programs can be added automatically from the New command. I realise I could just create one and then Open and Save As, but we (...) (25 years ago, 5-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | RcxCC Editor
|
|
First off, big thanks to DB for NQC, and MO for RcxCC. Both top products, and a major relief. Quick question though to Mark: I occasionally get corrupted text characters in the RcxCC editor window. The entire line that the cursor is on suddenly (...) (25 years ago, 5-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC wishlist
|
|
This works as a 1-based 16 element array of Boolean variables... // Boolean constants #define TRUE 1 #define FALSE 0 // Boolean storage - bye bye var 0 int bSys = 0; // Boolean array defines #define bool(i) ((bSys & (i^2)/2) == (i^2)/2) #define (...) (25 years ago, 5-Jan-00, to lugnet.robotics.rcx.nqc)
|
