>
>Hi Fabio,
>
>When did you do all this research! :)
>>
>I see your post, and ( for curiosity ) explain it into 2 minute,
>and write the message in 10 minutes !(sich)!
>
>
>Anyway, may it be a bug or a feature or an interpretation issue, one thing is clear. IF SET('STEP')='ON' in code is unreliable. My current advice is to use IF SET('DEBUG')='ON'.
>>
>No, sure it is not a bug, but it to be a VFP side feature.
Perhaps it's because I'm more alpha then beta, but for me it's not logical that it returns OFF after I've declared it ON.
>Sure it can to be usefull at design time.
>
>Example:
>If you write a monitor that check the developer work,
>or a monitor that build/test the program automatically this behaviour have sense.
>
>This monitor, with SET("Step") can known if the program is in suspend mode.
>
>This show a interesting behaviour of VFP VM:
>it is not a Multithread engine,
>but the it is not a simple sequential program engine.
In the Netherlands we have a new saying since a couple of years:
Every disadvantage has its advantage (Johan Cruijff)
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
