| |
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 can be started by direct commands, so it is
conceivable that someone would download a program which is only a
collection of tasks to be later invoked via direct commands. If I did add
this feature I'd have to make it optional. As soon as something requires
an extra option I start questioning its importance - there are lots of
subtle costs associated with options (documentaiton, testing, etc) so I
tend not to add them hap-hazardly (even so the NQC command line is a
beast).
I assumed that dead tasks or subs would be a very infrequent occurence
(thus not worth the cost of solving). If lots of people find themselves
with dead tasks or subs, please let me know. If demand for this feature
is high I'll put it on the list.
Dave Baum
In article <FntMB1.LqC@lugnet.com>, "WAN" <chv@crazyrobots.com> wrote:
> Hello,
>
> It would be great to have NCQ doing dead code suppression before
> downloading it to the RCX.
>
> Any function, task,... not referenced in the program should not
> be compiled and sent to the RCX.
>
> It would help to save memory and download time don't you think so ?
>
> - Christophe -
--
reply to: dbaum at enteract dot com
|
|
Message is in Reply To:
 | | NQC wish
|
| Hello, It would be great to have NCQ doing dead code suppression before downloading it to the RCX. Any function, task,... not referenced in the program should not be compiled and sent to the RCX. It would help to save memory and download time don't (...) (25 years ago, 4-Jan-00, to lugnet.robotics.rcx.nqc)
|
2 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
