LabVIEW style guide: Difference between revisions
Category reorg |
Added link to NI LV style checklist. |
||
| Line 1: | Line 1: | ||
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: | 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: | ||
*[https://www.ni.com/docs/en-US/bundle/labview/page/labview-style-checklist.html] | |||
*[http://www.ni.com/white-paper/5560/en/ Rules to Wire By Part 1] | *[http://www.ni.com/white-paper/5560/en/ Rules to Wire By Part 1] | ||
*[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] | ||
Revision as of 15:10, 14 June 2024
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.