LVOOP vs GOOP

[Ben]

---

@richjoh wrote:

How can you say "GOOP now uses the native LVOOP as a basis", its called Labview OOP not GOOP. What are the benefits besides maybe backward compatible (today) with legacy Endevo classes (I'm guessing here). 

Endevo never considered the debugging night mare and plenty of Endevo bewildered GOOP is running on test station. Yes the whole Endevo GOOP is a hack job on Labview, (ever look at the unlocked Endevo class creators (lots of overhead bloat LV code). Please explain how Endevo GOOP help out your projects.... enlighten me.

---

UML

Not supported in LVOOP (that I pronounce "La-voop" as if it was French "L'voop") but is available in the GOOP version. As of LV 2009 the two version were tied together and the first versions of the NI LVOOP course included some GOOP demos.

I do agree with your assesment of the implementation since the "core" of the GOOP version is what would have killed all of my high performance apps. For non-high-speed apps, and seasoned OOP types (that have all the design patterns memorized) it would be handy.

Just trying to help,

Ben

[JanK]

Since I work at Symbio, former Endevo, I just like to clarify info about GOOP and our tools.

1. We, Symbio, are still around as an NI Alliance Partner and working with LabVIEW and supporting our tools.

2. When LV introduced OOP we rebuild our GOOP to be based on LabVIEW classes and add by-reference. Main reason for still providing GOOP is that we wanted to be able to use the by-reference model as a complement to the by-value model used by LV classes.

3. Now we released GOOP4 which adds the by-reference by using DVR which gives better performance and very little extra code. You can use DVR and classes without our tool, we just made it more neat to use.

4. Our UML tool supports both LabVIEW classes and our GOOP4 class model. Code generation and reverse engineering.

5. The currently used NI OOP training was written by us originally in -97. It was rewritten when native OOP was introduced and now covers LV OOP plus our by-reference model

As a background the first GOOP was developed in -98 as a joint venture between NI and Endevo. It enabled OOP before there was any support in LabVIEW. It provided classes, but not inheritance.

In 2004 (or perhaps 2003), we released a better version which supports inheritance.

Thanks,

Jan