Graphical Object-Oriented Programming: Difference between revisions
m Added GOOP category. |
m Added link to new page "LVOOP Frequently Asked Questions" |
||
| Line 14: | Line 14: | ||
*[[History of GOOP]] | *[[History of GOOP]] | ||
*[[LVOOP|LabVOOP - LabVIEW Object-Oriented Programming (aka LVOOP)]] | *[[LVOOP|LabVOOP - LabVIEW Object-Oriented Programming (aka LVOOP)]] | ||
*[[LVOOP Frequently Asked Questions]] | |||
[[Category:GOOP]] | [[Category:GOOP]] | ||
Revision as of 22:22, 13 August 2007
This is the Portal for GOOP and LabVOOP.
GOOP stands for "Graphical Object-Oriented Programming." LabVOOP stands for "LabVIEW Object-Oriented Programming."
GOOP is a term used to refer to the various GOOP toolkits from Endevo/NI, SciWare and OpenG. These toolkits were written in G.
LabVOOP refers to the native LabVIEW classes that first appeared in LV8.2.
The toolkits were not obsoleted by the native implementation. All of the toolkits use a reference model for passing objects on the block diagram, similar to File refnums or Queue refnums in LabVIEW. The native classes pass by value, similar to clusters and arrays. The two mechanisms are complementary, not exclusionary, and there may be times when both approaches are used in the same LV program.