|
|
 | | RE: NQC wishlist
|
| (...) This might be a good idea. The pbForth thing is working out well too. Maybe a C to FORTH translator would be useful. In the other hand, making a custom bytecode interpreter means having to write the interpreter and support it on different (...) (25 years ago, 4-Jan-00, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | Re: NQC wish
|
| Inline functions are by their very nature surpressed. Also, most control structures and calculations that can be evaluated at compile time are eliminated. I thought about surpressing tasks and subs, but then decided not to. The problem is that tasks (...) (25 years ago, 4-Jan-00, to lugnet.robotics.rcx.nqc)
| | | | | Re: NQC wishlist
|
| (...) To me, one of the important features of such a thing would be compatibility with the existing firmware. Otherwise, why not just use LegOS? (25 years ago, 4-Jan-00, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | Re: NQC wishlist
|
| If anyone is seriously considering this I'd ask two things... 1) Have you considered porting the p-code interpreter used by Interactive C or something like a stripped down Java bytecode interpreter instead? The idea here would be that the RCX (...) (25 years ago, 4-Jan-00, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | Re: NQC wishlist
|
| (...) Yeah, this was discussed way back at the beginning of the reverse-engineering effort. It's something I'd like to see too. (25 years ago, 4-Jan-00, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
|
