Error ring excluded in executable?

[bokorpet]

Sure, if you share a reference (DVR), you have to make sure that no client destroys the reference while other clients are still using it. But this should not be an argument against sharing a reference, shouldn't it? For example, you can "hide" the reference in methods of objects and use access rights to control which client can do what (read, write, destroy, etc.).

In our project we implemented a shared memory which is a LabVIEW object and all clients own a DVR pointing to the object. Reads and writes of the shared memory are done via IPEs.

[Yamaeda]

A class DVR is the basis of G# to make it reference based and all data modification functions uses the IPS to modify data since it also encompasses a semaphor function. We have had no issues so far in that regard.

/Y

[NateBraska]

Hi Peter,

I have filed CAR 522606 for this Error Ring issue. Thanks for reporting it and for the nice example.

Best Regards,

Nathan Burke

Product Support Engineer | LabVIEW R&D | National Instruments | Certified LabVIEW Architect

[Hooovahh]

---

@NateBraska wrote:

I have filed CAR 522606 for this Error Ring issue. Thanks for reporting it and for the nice example. 

---

 I might have come to the party late, but I think it is clear that this is a compiler optomization problem, not an error ring issue.  I hope whoever looks into this reads this thread and realizes that.

[ChrisStrykesAgain]

CAR 522606 was fixed in LabVIEW 2017.