To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.nqcOpen lugnet.robotics.rcx.nqc in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / NQC / 533
    Re: NQC Ignores based on your pbrink —Dennis Williamson
   Have you considered adding the firmware build version to that symbol or to a new one? __RCX = 2 __FIRMWARE=3.21 This would facilitate creation of portable, work-around code that would accomodate an end-user who hasn't updated their firmware (or has (...) (24 years ago, 9-Apr-00, to lugnet.robotics.rcx.nqc)
   
        Re: NQC Ignores based on your pbrink —Dave Baum
   (...) This first define (__RCX = 2) will happen automatically in NQC when you select RCX 2.0 as the target for compilation. Selecting an RCX 1.0 target will cause the symbol to be defined as 1. (...) I hope I don't have to add a __FIRMWARE symbol... (...) (24 years ago, 9-Apr-00, to lugnet.robotics.rcx.nqc)  
   
        Re: NQC Ignores based on your pbrink —Matthew Miller
     (...) This seems reasonable to me. Plus, it has the added benefit of being inherently open: source is all about "here's how to do this"; binaries are "here's a thing that does this". It's nice to encourage the first attitude. (24 years ago, 9-Apr-00, to lugnet.robotics.rcx.nqc)  
    
         Re: NQC Ignores based on your pbrink —Dean Husby
     (...) I agree wholeheartedly. I don't want to see people selling their bot code. It's all about sharing and learning. Dean -- Coin-Op's For Sale!: (URL) Lego Workshop: (URL) Lego Club: (URL) (24 years ago, 9-Apr-00, to lugnet.robotics.rcx.nqc)
   
        Re: NQC Ignores based on your pbrink —Dennis Williamson
   I definitely intended to mean portable source. And that the "__FIRMWARE" would be used in compiler directives rather than in the code. It is a simple matter for me to define my own __FIRMWARE (or anything else, right?) and do #ifdef's to my heart's (...) (24 years ago, 9-Apr-00, to lugnet.robotics.rcx.nqc)
   
        Re: NQC Ignores based on your pbrink —Dave Baum
   (...) Yep, you can #ifdef however you want, and NQC supports -D and -U options on the command line that allow you to define (or undefine) symbols before the compile takes place. This is handy if you're using Makefiles, but even in an ordinary shell (...) (24 years ago, 9-Apr-00, to lugnet.robotics.rcx.nqc)  
 

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR