Comparing a VI to other textbased languages.

[Bodypilot]

To all you multi-linguistic programmers out there,

I'm afraid this is a bit off a �do-my homework-for-me� question but I don�t know of any other quick way of solving my problem.

I�m writing a thesis on software project management. As an introduction I�d like to write a chapter about LabVIEW.
It would be nice to be able to compare LabVIEW code to code written in some other language. Unfortunately I can�t program in anything but LabVIEW.

I�m hoping someone here would be so nice to �translate� the attach VI (writen in LabVIEW 7.0) into C or C++ code.

PS. The attached VI is really basic, so it should take to much time translating.

Waiting in humble anticipation,
Bodypilot

[LesHammer]

I don't have LabVIEW 7.0 installed on this computer, so I can't open your VI, but in general translating between graphical and text based languages (or vise versa) gives an "unfair" comparision. It's like translating a joke from one language to another and then concluding that the first language is better for jokes than the second language because the translation failed. I've had simple text based language programs become complex LabVIEW programs, and simple LabVIEW programs become long text based programs. Much depends upon the paradigm of the language.

Les.Hammer@CompleteTest.com

[Wiebe@CARYA]

Hi,

I couldn't agree more. Right now I'm working on a linked list in assembler
(for a hobby). This is very convenient in asm, because working with pointers
is 'native' to asm. As a result, the data that I can put in the linked list
can vary. I wouldn't even try to do this in LV, but then.. why should I? LV
has such great array functions there is no need for it! This is just one
practical example why it's unfair to compare code between languages.

Beside the resulting code, what about compairing development time?

Regards,

Wiebe.

"Les Hammer" wrote in message
news:50650000000500000030310100-1066448259000@exchange.ni.com...
> I don't have LabVIEW 7.0 installed on this computer, so I can't open
> your VI, but in general translating between
graphical and text based
> languages (or vise versa) gives an "unfair" comparision. It's like
> translating a joke from one language to another and then concluding
> that the first language is better for jokes than the second language
> because the translation failed. I've had simple text based language
> programs become complex LabVIEW programs, and simple LabVIEW programs
> become long text based programs. Much depends upon the paradigm of
> the language.
>
> Les.Hammer@CompleteTest.com