Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Instantiation of an object
Message
From
03/12/2008 01:41:05
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Germany
 
 
To
02/12/2008 17:51:59
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Classes - VCX
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
Visual FoxPro
Application:
Desktop
Miscellaneous
Thread ID:
01365028
Message ID:
01365318
Views:
9
>>>> I have a class library called MyClass.vcx, which has several objects within it (including forms) - I use the command goMyClass = createobject('MyClass') to > instantiate the object, but the question is this:
>>>
>>>This line implies that you have a class 'MyClass' in some classlib (I'm kind and assume you have used SET CLASSLIB TO MyClass.vcx without mention)
>>
>>
>>thats not exactly what came into my mind but it shows in how many ways this could be misunderstood <s>
>>
>>
>>>I myself call it rubbish to name a class the same as the vcx.
>>
>>Full ACK
>
>Unless you have a single class in the vcx - then it serves no purpose to have separate names. I've worked in a place where the forms were kept in classlibs, one per vcx - in that layout, vcx==class. Of course, framework stuff was n classes 1 vcx, and then none of the classes was named the same as the vcx.

You might call (and use) it as you like. It's just a matter of taste. I was giving my POV analyzing the initial message only.
I prefer a kind of hungarian notation. So my lib would be something like "people.vcx" and the classes would be like "frmNames", "de_Names" and so on.

Agnes
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord

Weeks of programming can save you hours of planning.

Off

There is no place like [::1]
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform