Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
#DEFINE - Why?
Message
From
31/03/2008 12:44:32
 
 
To
31/03/2008 12:37:12
Jay Johengen
Altamahaw-Ossipee, North Carolina, United States
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Environment versions
Visual FoxPro:
VFP 9 SP2
Miscellaneous
Thread ID:
01306848
Message ID:
01307023
Views:
9
>>>>>>>>What is the simplest explanation as to why these are needed? Why not just set regular variable values? So what if they are constant and don't change?
>>>>>>>
>>>>>>>Security of the source code so that reverse engineering of an application won't give back that code.
>>>>>>
>>>>>>Good additional point.
>>>>>
>>>>>Give back what code?
>>>>>
>>>>>It would show "10" instead of "My_Constant" in the source. Is that a big security issue? Enough to not put it in a variable? It can only be done for constants, so constants are the only things that would be protected. Is that a valid security reason to use DEFINE?
>>>>
>>>>You got it wrong. When your source code is Re-foxed, the constants will remain as is (I'm guessing), e.g. you would not get your code as it was written originally with #DEFINE.
>>>>
>>>>That was Denis point, as I understood it.
>>>
>>>What part did I get wrong? That only the constants are protected?
>>__
>>
>>Oh, it's getting in slowly ...
>
>I didn't get that. Are you trying to be clever? How is all the source protected if I use one DEFINE?
__
Jay,

What I'm getting is the impression that you don't even read what others post.
You immediately respond that you do not agree
Gregory
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform