LabVIEW style guide: Difference between revisions
Created page with links to Rules to Wire by and VI Analyzer |
mNo edit summary |
||
| Line 4: | Line 4: | ||
*[http://www.ni.com/white-paper/4822/en/ Rules to Wire By Part 2] | *[http://www.ni.com/white-paper/4822/en/ Rules to Wire By Part 2] | ||
These guidelines in programming style are important and can be check through automated inspection using the [[VI_analyzer VI Analyzer]] toolkit. | These guidelines in programming style are important and can be check through automated inspection using the [[VI_analyzer|VI Analyzer]] toolkit. | ||
Revision as of 15:45, 15 November 2018
LabVIEW is a graphical programming language, and as a result emphasis is often put on how the code looks, as well as how it performs. Developers may have preferences on one style or another, but one good starting point is the following NI White Papers on Rules to Wire by:
These guidelines in programming style are important and can be check through automated inspection using the VI Analyzer toolkit.