Subject:
|
Re: NQC wishlist
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Fri, 7 Jan 2000 03:31:39 GMT
|
Viewed:
|
2121 times
|
| |
|
|
In article <FnwsJJ.n35@lugnet.com>, "Ben Jackson" <ben@ben.com> wrote:
>
> BTW, I almost always type SetDisplay() first and usually get as far as
> compiling it once before I remember the incongruity...
The inconguity was intentional. I was going to call it SetDisplay(), but
then it seemed like:
SetDisplay(1)
should set the display to show the value 1. I felt that "select" did a
better job conveying the fact that there are 7 different display modes and
you select one of them.
I'm not saying that this is a "great" argument, or that the naming is
ideal...just that there was at least some thinking behind it. What I'd
really like is a bytecode to allow us to do a real SetDisplay()!
Dave Baum
--
reply to: dbaum at enteract dot com
|
|
Message is in Reply To:
 | | 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)
|
17 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
