https://labviewwiki.org/w/index.php?action=history&feed=atom&title=Object_%28object-oriented_programming%29Object (object-oriented programming) - Revision history2026-04-21T10:30:00ZRevision history for this page on the wikiMediaWiki 1.43.0https://labviewwiki.org/w/index.php?title=Object_(object-oriented_programming)&diff=12308&oldid=prevLogmanoriginal: Add new page2020-04-03T07:40:01Z<p>Add new page</p>
<p><b>New page</b></p><div>In [[object-oriented programming]], an '''object''' is a specific instance of a [[class (object-oriented programming)|class]] in memory.<br />
<br />
==Objects in LabVIEW==<br />
<q>LabVIEW has a pure by-value syntax for its objects. When a wire forks, the object may be duplicated, as decided by the [[LabVIEW compiler]].</q><ref name="lvoop-decisions">[https://www.ni.com/en-us/support/documentation/supplemental/06/labview-object-oriented-programming--the-decisions-behind-the-de.html LabVIEW Object-Oriented Programming: The Decisions Behind the Design] by National Instruments</ref><br />
<br />
<q>An object is a self-aware piece of data. It knows its own type (that is why objects can perform operations such as [[To More Specific Class function|To More Specific Class]] and [[dynamic dispatching]]).</q><ref name="lvoop-decisions"/><br />
<br />
<q>LabVIEW allocates a single instance of the default value of the class. Any object that is the default value shares that pointer. This sharing means that if you have a very large [[array]] as the default value of your class there will initially only be one copy of that array in memory. When you write to an object’s data, if that object is currently sharing the default data pointer, LabVIEW duplicates the default value and then perform the write on the duplicate. Sharing the default instance makes the entire system use much less memory and makes opening a [[VI]] much faster.</q><ref name="lvoop-decisions"/><br />
<br />
==References==<br />
<references/><br />
<br />
[[Category:Object-Oriented Programming]]</div>Logmanoriginal