Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Using preprocessor directive when in IDE
Message
 
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 9 SP1
Miscellaneous
Thread ID:
01320008
Message ID:
01320056
Views:
16
>>>>>>You can only use built-in functions in #IF.
>>>>>>To control what to compile, you would use #IFDEF/#IFNDEF in combination with #DEFINE/#UNDEF
>>>>>>
>>>>>>>
>>>>>
>>>>>By built-in functions do you mean those that are compiled? And if I use #IFDEF/#IFDNED, I still can't use them when running/testing the application in IDE, right?
>>>>
>>>>You can probably define something like
>>>>
>>>>#DEFINE DEBUG .T.
>>>>
>>>>Then
>>>>
>>>>#IF DEBUG
>>>> My IDE Code
>>>>#ELSE
>>>> My Production Code
>>>>#ENDIF
>>>
>>>I need to have two production codes depending on some constant.
>>>
>>>Thank you for your suggestion.
>>
>>Do you want to include this into your final code or have two separate versions of the code not compiled? Can you work along the lines above?
>
>I want to include in the final EXE only one version of the code. But when I am testing the application (in IDE) I want to be able to run this or that code. I thought I could do it by setting or defining some global variable. But it does not seem to be possible.

When you want to test one version of the code do

#DEFINE ONEVERSION .T.

#IF ONEVERSION
My First code to test
#ENDIF

When you would like to test a different version you would change your code to false.

Same way in C# with the difference that #DEFINE only creates a variable (not sets value).
If it's not broken, fix it until it is.


My Blog
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform