LabVIEW
Refactoring LVOOP
wrote:
wrote:
Moving private data from several childs to the parent will be very tricky. I don't think I'd like LabVIEW to do that. What happens to unbundles in the child methods? Replace them with VI's? What if in placement structures are used? The VI's have error handling. Should it be used? The clusters didn't... It will create a mess.
Well, this is why there is a recommendation to only ever access private data via inlined accessor VIs (No Errors).
It feels like overkill when dealing with classes, but it makes refactoring a whole lot easier.
But the question is: do you trust LabVIEW to make choices like that?
If this was done automatically, LabVIEW needs to be able to do it 100% reliable, and I don't think that can be done. There are just too many factors to take into account.
Search LabVIEW like a graph! 