LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

array allocating more memory

Highlighted

ritesh024 wrote:

One more thing, What do you guys mean by "In Place" ??

Is it simply "In Place Element Structure" or something else ?


You operate on an array "in place" if there are no new buffer allocations. For example "replace array subset" can operate "in place" while "insert into array" cannot. The LabVIEW compiler can often determine if things can be done "in place" and does it automatically without any special action needed.

 

The "in place element strucuture" is a more advanced tool that gives you more control on how the compiler handles things internally. It is often not needed because LabVIEW knows what to do. 🙂


LabVIEW Champion. It all comes together in GCentral GCentral
Message 21 of 24
(292 Views)
Highlighted

ritesh024 wrote:

One more thing, What do you guys mean by "In Place" ??

Is it simply "In Place Element Structure" or something else ?

I have gone through many posts and found it a very common term, but could't get it in the right context.

 


See here and here and here.

 

And if you are still curious (and have brains cells left) see these tags and all of the tags in this cloud.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 22 of 24
(291 Views)
Highlighted

You operate on an array "in place" if there are no new buffer allocations. For example "replace array subset" can operate "in place" while "insert into array" cannot. The LabVIEW compiler can often determine if things can be done "in place" and does it automatically without any special action needed.


Well thanks altenbach for such a simple and precise definition. :smileyhappy:

 

 

Isn't there a method to dynamically alloate memory to the previous array and not make copies of the new array?

Something like we can do with Pointers in C/C++.

Bcoz memory is sometimes a BIG issue in many of the applications and many a times it is not known before hand of much of data will be required. So, using "Insert into array" all the time to create memory dynamically will cause nightmares to the programmers.

 

0 Kudos
Message 23 of 24
(286 Views)
Highlighted

@ritesh024 wrote:
OK. But how will it be more efficient on using FB node over the USR?

Ok.I found the ans at LabVIEW artisan blogspot.

 

 

but i am still struggling hard to know about allocating memory dynamically without causing extra copies of data but rather adding memory to prevoius array.

 

0 Kudos
Message 24 of 24
(269 Views)