LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
JICHFI

Pointers in LabVIEW

Status: Declined

Any idea that has received less than 4 kudos within 4 years after posting will be automatically declined.

When I need to pass a data from a loop to another I need to create an indicator and local variables which create copies in memory for each variables. So we have at least 3 copies in memory for the same data. One for the wire itself, one for the indicator and one for the local variable. Why there is no kind of pointers which LabVIEW could handle from under the hood with the wire's memory adress. Imagine something like that. Then we don't need to use a hidden indicator only for data passing.

pointer.PNG

This example doesn't look very clever but you can see what I mean. 

2 Comments
tst
Knight of NI Knight of NI
Knight of NI

There have been numerous other ways of passing data between loops for a long time (e.g. notifiers, queues, LV2 globals). A single element lossy queue, for instance, would not create a copy of the data.

 

In any case, LV 2009 includes a feature which is specificially supposed to handle what you want - the references to data feature. It's NOT pointers, but it does serve the use case of guaranteeing a single copy of the data in memory. That said, you might find that the implementation has some thing which you won't like.


___________________
Try to take over the world!
Darren
Proven Zealot
Status changed to: Declined

Any idea that has received less than 4 kudos within 4 years after posting will be automatically declined.