Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Parsing expressions defined by end users
Message
From
29/04/2016 03:59:15
 
 
To
29/04/2016 03:22:04
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 9 SP2
Miscellaneous
Thread ID:
01635536
Message ID:
01635618
Views:
52
>>I think you need to determine between operator and operand too. It is bad practice, but it will work to do something like
>>
>>EXECSCRIPT ='Mooh'
>>?EXECSCRIPT+'!'
>>
>>This something different then
>>
>>EXECSCRIPT(somethingunwanted)
>>
>>
>>This is only an example, it's clear that the twoliner will not work, but you have to consider this. Some functions are valid, others not, and not each in all circumstances.
>>
>>Report is even worst, since the datatype of a reportfield is something the user might change for good reason.
>
>Functions names are distinguished from variables names by the ( suffix. For hazard checking it would be enough, wouldn't it? For the rest, the VFP processor would complain during evaluation.

One thing to be careful of is space(s) between a function name and the "(" e.g.
?SQRT ( 2 )
Regards. Al

"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov

Neither a despot, nor a doormat, be

Every app wants to be a database app when it grows up
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform