Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
BUG: return a new object by reference fire a C5 crash
Message
 
 
To
16/04/2004 02:14:54
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00893984
Message ID:
00897089
Views:
16
Bob,

>This is the solution we had to make to every assign method that was written for object members.

You have me curious here about the root scenario that leads to conditional setting of the object ref.

I've used a lot of member object access methods to provide delayed instantiation of "high cost"/"infrequently used" objects ala:
* oXML_access
if ( isnull( this.oXML ) )
   this.oXML = createobject( ... )
endif

return this.oXML
But I don't think I've ever come across a reason to even create a member object assign method, much less make it conditional, so I'd just like to hear about the reasons where you've run into it.

>It wasn't fun, but our development environment now runs w/o C5's

Hopefully you can yank that code all out with some future release.
df (was a 10 time MVP)

df FoxPro website
FoxPro Wiki site online, editable knowledgebase
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform