Questions about using a reference held in private class data without changes to the reference value

[cbutcher]

So, I have a bunch of boilerplate code that looks like variations on the following:

Here, you can see an IPE Structure, with unbundle/bundle of a (COM, but it doesn't matter afaik for this question) reference. Then I do something with the reference using a property or invoke node (here invoke). The reference coming out of the node is to my understanding identical in every way to the one entering the node.

Whilst looking for the suitable way to do this in a child class (using the same private data, but now belonging to a parent and so inaccessible directly using an IPE) I came across this idea post in which the problem is discussed. There, AQ tells the OP that starting in 2013, LabVIEW will use inline accessors in the same manner as an IPE, subject to some conditions regarding their placement.

AQ also describes how ideally APIs should discourage wiring 'object out' indicators from 'Read' accessors, in order to avoid artificial dataflow constraints.

My question becomes, should I instead do this:

and use a 'Read' only accessor when in a child class, like here (same VI, so not actually a child, but the point should be clear):

(in this case, I have an object out indicator - my bad, but it does make it 'nicer' looking, and here the outcome should be identical I think - just a fork in the wire from in to out in the inlined subVI, which has nothing more than an unbundle node)

[crossrulz]

In this case, I would make protected methods in the parent class for the common actions on the reference.  This might even remove the need for the accessor VI.  With the VI in the Protected access mode, only children can use the method.