Functional global with too many terminals

[Yamaeda]

For i'm stuck might not handle two beers, send one my way! 😄

[JÞB]

---

@for(imstuck) wrote:

---

@Mark_Yedinak wrote:

Oh look at you Greg. Quite the name dropper.

 

(Just giving you a hard time)

---

Debated long and hard about the name drops, actually. But, I decided they help to improve credibility. 

Oh, the wise LabVIEW Champion Mark Yedinak once called me a name dropper, and then I made him buy me a beer at NI week.

---

The word of a Trusted Enthusiast isn't good enough?

[crossrulz]

---

Jeff·Þ·Bohrer wrote:

The word of a Trusted Enthusiast isn't good enough?

---

Apparently not.  Not enough logos in his signature.

[Bublina]

A bit off-topic;

To reveal a knowldge I have not found anywhere in LabView help.

If you have a subVI that takes big chunks of data as input and proceeds with some algorithm, if it is possible allways inline that subVI.

I had this simple algorithm, that was cutting out some array subset. Algorithm itself took 0ms, the subVI itself took 500ms. After inlining, the subVI itself took 0ms.

[Intaris]

You should NOT inline a funtional global because you lose all statefullness by inlining.....

Unless you've got a constant referring to a Queue or DVR in there the FGV won't work when attempting to share data between processes.

[Bublina]

I was writing about subVI, not FGV. Yes the subVI is in FGV 🙂