Quote:
Originally Posted by Tom Line
Bingo.
If I jumped into C++, ignored classes, subroutines, and just trie to write everything out line-by-line, it would be ugly.
Just because you don't understand or haven't been taught how to write clean LabView code doesn't mean it isn't clean.
One basic rule: If your code gets bigger than one or two screen-widths, you're getting too complicated and not splitting it up into Sub-VI's efficiently.
There's a whole host of other rules, but being that this is a Visual language, if you can't tell from a glance what it's doing, you're probably doing it wrong.
|
The code I saw was incredibly complicated due to it being for some piece of random hardware. It was pretty messy. But you are correct, it does depend on the programmer and his/her practices. Our code is definitely a mess because nobody bothers to take the time to write it cleanly or clean it up after build season. Splitting projects into Sub-VIs (much like splitting a C++ project into different source and header files) would make things much neater. I think LabVIEW would be a nice thing to know, but I don't see myself using it for something as relatively simple as the robot code.
Alex Brinister