LabView

[CraigGraham]

Seasoned LabViewer

Lab Viewer wrote in message
news:5065000000050000003C480000-1002247793000@exchange.ni.com...
> In order to avoid complains regarding 'The Evolution' let's append
> this picture to it 🙂
> Thus, the LabVIEW proGrammer will be in … and I think that even
> the Chief Executive will understand 🙂



[Attachment image.jpg.JPG, see below]

[JeanPierre]

Obscure LabViewer.





[Attachment Hello.vi, see below]


[Attachment Hello.jpg, see below]

[Enrique]

Now this blew my mind!

Although I was able to replicate the result (imagination and dark tricks are required), I have no idea what is going on...

[Mikael_Garcia]

Enrique and Brian,
This is probably how Jean-Pierre did his trick. /Mikael

[Brian_Vibert]

Thanks, but I figured that part out. It just doesn't make much sense to me 🙂

[Mikael_Garcia]

I know. It is silly. However, let me guess what is going on here.

I think the data type string and a boolean array both are coded as a sequence of bytes. The string "ABC" viewed in hex mode is "41,42,43". And the Boolean array "True, True, False" is coded as "01,01,00". Both taking up three bytes. The type cast function transforms a the string to a Boolean array by doing basically nothing to the bytes stored in memory. But in LabVIEW we see a Boolean array that has bits instead of bytes. And if a byte is not equal to "00", the bit in the Boolean array is displayed as False. If you make a change to one of the elements in the Boolean array you cannot re-create the text by changing it back. This shou
ld then be the result of that LabVIEW writes either "00" or "01" in the position and thus erasing what was there before. Oh, well. This is just my speculation... /Mikael

[JeanPierre]

Bingo Mikael!

You are now Great Knight of LabVIEW Obfuscation |?)

Jean-Pierre

[tom]

If I might add my tuppence worth. I was brought up in the days of
Fortran77
and did all my research and scientific programming in that minus all the

fancy GUIs. I tried to move over to C and found it a nightmare in
comparison, difficult to read and it did not even have complex numbers!
Added to that it was difficult to
port from platform to platform. (despite the claims of ANSI standard)
Now I can see the beauty of C for low level I/O
tasks and GUIs (C++) but not for Scientific number crunching.
LabVIEW on the other hand has renewed my faith in programming. It is
a bold and oroginal step away from the old methods and one day I fully
expect to outperform all the rest.What really surprised me recently is
that
m
athematicians in some areas (parallel number crunching) still use
Fortran!
I think LabVIEW is for Engineers and Scientists - C for programmers with

plenty of time on their hands.

Tom


Jean-Pierre Drolet wrote:

> Bingo Mikael!
>
> You are now Great Knight of LabVIEW Obfuscation |?)
>
> Jean-Pierre

[CraigGraham]

Here's something that had me bewildered the first time I (accidentally)
achieved it. True Programma Obscura. 🙂


Jean-Pierre Drolet wrote in message
news:3bd09761@newsgroups....
> Bingo Mikael!
>
> You are now Great Knight of LabVIEW Obfuscation ??)
>
> Jean-Pierre
>
>



[Attachment Wierd.vi, see below]

[Enrique]

cheap and low... and it doesn't say "Hello World"

😛

.