Actions
Forum Thread Details
  • Replies 3 replies
  • Subscribers 178 subscribers
  • Views 422 views
  • Users 0 members are here
Related

Using eagle3d inc files in test mode

Former Member

This is something that I cant get working.

Maybe I am following a wrong approach.

 

If I render this simple piece of code always the 100n component is rendered

whatever I use in the the declare.

 

#declare inc_testmode = on;

 

union{

#ifndef(inc_testmode)

        object {CAP_DIS_WIMA_25_025_046_075("10n",)}

#else

        object {CAP_DIS_WIMA_25_025_046_075("100n",)}

#end

 

Why is this so be course I cant find anything in de doc.

 

 

Parents Reply Children
  • in reply to Former Member

    It doesn’t matter if I declare inc_testmode, always the else statement is

    executed.

    maybe I should remove all de ifdef;s and replace them by simple if

    statements.

     

    "fred"  schreef in bericht

    news:MPG.2aee1b533f6acc07989692@news.virginmedia.com...

     

    In article <k5uumq$a9u$1@cheetah.cadsoft.de>, info@oldtimetech.nl

    says...

     

    This is something that I cant get working.

    Maybe I am following a wrong approach.

     

    If I render this simple piece of code always the 100n component is

    rendered

     

    I'm not familiar yet with ULP but standard practice for preprocessor

    directives say that ifdef ifndef etc will be true if the label is

    defined (ie thats what its there for)

     

    i.e. ifndef does not relate to a value - just the existance of the label

     

    You should find this to be the case in any language.

     

     

  • in reply to Former Member

    In article <k65pmo$92r$1@cheetah.cadsoft.de>, info@oldtimetech.nl

    says...

    It doesn?t matter if I declare inc_testmode, always the else statement is

    executed.

    maybe I should remove all de ifdefs and replace them by simple if

    statements.

     

     

     

    You dont normally want to just swap #ifdef's with #if's because they

    mean different things (if you understand that then by all means do of

    course)

     

    I havnt used POVray for around 20 years so I'm not sure of the correct

    syntax you can use.

    There should be a .chm file though -

     

    My guess is this is a simple case of the token being defined in an

    include somewhere (the "= on" is irrelevant to the #ifndef)

     

    change it to

    #declare mytoken;

     

    #ifndef (mytoken)

       do(10)

    #else

      do(100)

    #endif

     

    or whatever the correct sytax is - and swap it to see if it changes

    if it does - you have a duplicate  - probably in an include file

    if those are in scope in povray now