Rube Goldberg Code

[Coq_Rouge]

---

@Steve Chandler wrote:

This construct is very similar to the first reply in this thread. Maybe the following code was posted in one of the other many replies.

Found in a code review.

---

There's too much confusion
can't get no relief
Buisness men they drink my wine
Plowmen dig my earth
None would ever compromise
Nobody of this world

[SteveChandler]

Plot Images.vi found with the example finder is not exactly an RG but there is some pointless code.

Spoiler

I am guessing this was originally written before LabVIEW had the event structure and #3 was overlooked.

[altenbach]

A simple array transformation apparently needs a lot of code (top). The bottom shows an equivalent alternative, too simple! 😄

 

Note that LabVIEW is actually smart enough to fold most of the while loop code ("transpose", "array size", "index array", "-1"), because it is loop invariant. WIthout this feature, we would repeat e.g. the same transposition on the same data N times in a row.

(seen here)

[JÞB]

Found in Agilent 34790.Lvlib:List to array

Spoiler

(c) 2005-2010 National Instruments.  ALL RIGHTS RESERVED.

 for whatever its worth I think the string searches in the upper case call the split string function anyway but I won't bother benchmarking either

[altenbach]

That "continue if true" is a hint that this is ancient...

[altenbach]

Just when you thought you've seen it all, a VI gets posted that pushes the boundaries a little bit more.

Just look at the navigation window. It actually brings LabVIEW to its knees. redrawing the navigation window is really sluggish on my machine. 😄

(seen here. Also notice that some people program the same way as they compose post titles ;))

[altenbach]

The curious case of the blue booleans!

Is there a reason to temporarily convert booleans to numbers just do do some boolean operations?

(seen here)

 

(Of course we would also have e.g. "in range and coerce" to simplify things even more ;))

[JÞB]

---

@altenbach wrote:

The curious case of the blue booleans!

Is there a reason to temporarily convert booleans to numbers just do do some boolean operations?

---

To do it just like it was developed in VB.  (If I remember my text programming correctly)

[Silver_Shaper]

Really this thread is very good and very much useful.. My hartley thanks to the author.

[Ray.R]

---

@altenbach wrote:

The curious case of the blue booleans!

Is there a reason to temporarily convert booleans to numbers just do do some boolean operations?

(seen here)

 

(Of course we would also have e.g. "in range and coerce" to simplify things even more ;))

---

I've been digging through code tha looks like this for the past month..

Except for the locals..