Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Using Proper case for PEM- does it bloat VCX?
Message
From
12/02/2010 09:13:24
 
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Vista
Network:
Windows 2003 Server
Database:
MS SQL Server
Miscellaneous
Thread ID:
01448817
Message ID:
01448920
Views:
63
This message has been marked as a message which has helped to the initial question of the thread.
Naomi --

There's always been a split in the VFP community about MemberData usage ... yes, there are some performance hits, but it increases readability a lot.

I use it all the time, and have never been aware of any performance degradation doing so.

No doubt it depends on the machine your working on, the configuration and depth of your class structure, and how sensitive you are to speed issues.

In any case, if you are using PEM Editor, there's a preference item so that it won't create _MemberData if it doesn't already exist.

>>>Hi everybody,
>>>
>>>Just wondering if using proper case for methods and properties significantly increase size of VCX. Does anyone have any statistics about the size increase or VCX / SCX?
>>>
>>>Thanks in advance.
>>Nadya,
>>
>>I do not recommend _memberdata formating in base classes. It seems to slow down the IDE on a high value (it get computed over and over, let's say for a textbox). I had it once but kicked it.
>>
>>I have decided to put the formated PEMS into the intellisense dbf, it is much faster. Only PEMs for "end use" classes will be stored within the vcx.
>>
>>HTH
>>
>>Agnes
>
>Thanks, Agnes. I downloaded PEMEditor yesterday and added a few new properties and methods. I will add them in lower case from now on to avoid the bloat and speed reduction.
Jim Nelson
Newbury Park, CA
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform