Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
CreateObject() vs NewObject()
Message
From
25/08/2007 19:50:08
Mike Yearwood
Toronto, Ontario, Canada
 
General information
Forum:
Visual FoxPro
Category:
Classes - VCX
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP1
Miscellaneous
Thread ID:
01249678
Message ID:
01250470
Views:
35
>Hi Mike,
>
>Interesting, I never saw this reply until now...
>
>>If newobject closes all open classlibs and then reopens them that has to be slower than scanning a string, especially if they're not compiled in an exe/app.

Wellll, I guess from a certain perspective, I don't use classlibs nor procedure files myself. All UDFs I make are separate entities, uniquely named and reusable. Even procedures are standalone, calling out to UDFs (each in their own file) as if they were extensions of VFP itself. I use a vcx (when I do) because I have no choice. I use a PRG as a design time container for a single class, and wish I didn't have to set procedure to to use them, just as I don't have to set procedure to to use a UDF in a PRG.

Mike


>
>But my point was that if you never use procedure files nor classlibs, there is nothing to open / close, except those opened by third party products (aren't you already hating them, the source of all our problems? <g>)
>
>
>>Picky, picky! ;) I'm only trying to use some pseudo pseudocode to say "detect if the specified vcx file name is already opened/available/whatever" which in this case is easier said in code.
>>
>>How about "\VCXNAME.VCX" $ SET('CLASSLIB')
>
>Sounds good to me, sorry to be picky <g>

np :)
Previous
Reply
Map
View

Click here to load this message in the networking platform