| | 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)
|