Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Spellbound - EVAL() in VFP6 needs to be macroed in VFP9?
Message
From
20/09/2006 08:08:48
 
General information
Forum:
Visual FoxPro
Category:
Classes - VCX
Environment versions
Visual FoxPro:
VFP 9 SP1
Miscellaneous
Thread ID:
01155368
Message ID:
01155459
Views:
42
A very fine example on how a missing or incomplete naming convention can/will cause trouble! Personally I would never use for example cString as a variable, I would always precede it with a letter to indicate the scope. I would use lcString for local, pcString for private and gcString for glogal. A field on the other hand I coull call cstring.

>Hi Fabio
>
>>
>>* try
>>cSource   = THIS.CheckSource
>>
>>cContents = EVALUATE(m.cSource)
>**==>Great guns, this above code executed, I guess the m. did it *g*
>
>>* post
>>? FSIZE("cSource")=0 && check fields name not exists
>**==>.F.
>
>>? [cSource]=="cSource" && check include preprocess not exists
>**==>.T.
>>
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform