How is re-entrancy managed in LVOOP Object Oriented

Question

Hello my fellow LabVillians,
I have yet another question from the land of object oriented programming.
My application uses multiple serial ports and architecualy it made sense to have a common serial driver object and re-use it around my code.
To my surprise, different object instances share (Lock) methods.
My surprise being that this is kind of a fundamental princliple of OOP: Data and Methods Encapsulated within each object.
I guess I understand that that some conditions would need Functional Global Variables,  I had assumed that they weren't possible/Practical in OOP.
After I finished having My tantrum and changed the Class .vi to be re-entrant (Share clones is compusory) I found the Following:
1. During Deployment I got a "Lost connection with Target"
2. A broken Arrow
3. Soon after a Labview Crash.
This is pretty repeatable and incredibly annoying.
Anyone else seen similar behavior?
Any one else have an opinion about Object Methods and re-entrancy?
LV11sp1
Kind Regards,
Tim L.
iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT

Answer 1

I suspect you have some other issue in your code. We extensively use both LVOOP and reentrant methods without any issues. In fact, one of our classes is a communications class which supports serial, parallel, USB, Blue Tooth and TCP interfaces. All of our methods that will not effectively execute immediately such as a methods to set or get an attribute are reentrant.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot