A call for obfuscated LabVIEW code

[shoneill]

Any chance of saving a few of these in LV 6.1?

Shane.

[altenbach]

Shane,

Sorry, my 7.0 installation is currently broken/corrupt so I cannot go back to 6.1. I need to reinstall first. 😞

[altenbach]

Just another variation on the theme 😉
(Converted to 7.0 from 7.1, but I cannot test if it works in 7.0)

[tst]

Altenbach, that first one was clever. I am puzzled about the second one, though. Why do another type cast one? Is there significance to the date? I know it's not your birthday since that was only a week or two ago.

[altenbach]

Yes, I agree that last one was pretty dumb, I was just playing around with other data types to see how much fits.

Time to drop the type casting and do something more creative and get away from the "Hello World" theme. I think JP grabbed the "hello world" trophy a few days ago anyway. 🙂

[JeanPierre]

We still need to define the rules.

What is the purpose of the VI (saying Hello World or somethingelse)

Some basic rules:
1. No hidden/transparent/invisible objects.
2. No masquaraded objects. subVI icons can't mimic native functions/objects.
3. No external code (CIN, CLN, ActiveX, etc.)
4. No external data (from file, TCP, HTTP or any other source)
5. Are subVIs allowed? maybe just vi.lib?

[altenbach]

I agree with 1-4. Maybe subVIs need to be allowed. I still remember your millenium.llb from the end of 1999. One of the subVIs had amazingly little code! 🙂

(Maybe you should post it again. I still have a copy).


The purpose should be wide open to interpretation. A VI might not have any useful purpose at all except to show some creative programming.

Message Edited by altenbach on 03-30-2005 04:39 PM

[tst]

I ran the millenium VI on LV7 and I had a problem with the text part. The text window appeared to be under the graph window and the text didn't appear even when I moved the other window, so the VI seemed not to do anything. If you plan on reposting it, you might wanna make sure it still works as it should. Great VI, by the way.

[Ray.R]

Hummmm....

I'd vote for no sub-vi..

Well... maybe allowing a limit on sub-vi's..
We wouldn't want to create a ton of sub-vi's just to hide the meaning of the code..

Do we need to define what is "obfuscation"? or do we leave that to everyone's interpretation and creativity??

R.

[Ben]

Hi All,

The rules as stated seem good.

Re:sub-VI's
I say let em fly.

Re;What is Obfuse

I hate to say it but JP's VI is not.

It is elegeant!
It is intructive!

Not obfuse.

On the other hand Altenbach's posts prior to JP's were obfuse.

But this is just my opinion.

In the end we were going to vote on what we thought ws obfuse.

Here is my submission.

It will only run in LV 7.1 and it needs write access to the folder where is running from. It also has a safety feature that prevents it from working if it is re-named. With all of those restrictions I have probably given away the game but who cares.

Ben