Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Joel on Software
Message
 
To
17/05/2005 09:05:27
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
01014573
Message ID:
01014904
Views:
21
If I might, let me insert a thought here.

Assuming that your application object is attached to _Screen, and all
other system objects are attached to _Screen.oApp, then from that point
on, all you would ever need are local variables.

By using LPARAMETERS instead of PARAMETERS, parameters variables are thenlocal,
as they should be, so scope indicators are not necessary.

You could also use 'tcCustName' instead of 'cCustName' for parameter variables.
I see no point in adding the 't' in front of a parameter variable.

And if you define all variables as local, then a scope designator is no longer
necessary. Therefore, all thats really needed is the data type indicator. Some
examples:


lcCustName --> cCustName
lnOrdAmt --> nOrdAmt
_Screen.oApp.oMenu


I find this much more readable, and easier to maintain.



>>I don't use "Hungarian" but I have a simple personal rule for your example... your lnAccountNumber would be AccountNumber and you lcAccountNumber would be AccountNo.
>>
>>Works nicely for me.
>
>It works for you, but have you documented it anywhere so that the next person who has to work on your code will know what you've done?
>
>Tamar
Everything makes sense in someone's mind
public class SystemCrasher :ICrashable
In addition, an integer field is not for irrational people
Previous
Reply
Map
View

Click here to load this message in the networking platform