Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
CreateObject() vs NewObject()
Message
 
To
24/08/2007 14:49:38
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:
01250410
Views:
31
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.

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>
"The five senses obstruct or deform the apprehension of reality."
Jorge L. Borges?

"Premature optimization is the root of all evil in programming."
Donald Knuth, repeating C. A. R. Hoare

"To die for a religion is easier than to live it absolutely"
Jorge L. Borges
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform