LabVIEW style guide: Difference between revisions
Category reorg |
Added links to style guides. |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
*[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] | ||
Additionally, there are checklists and style guides that contain more detail when ensuring consistency of style in LabVIEW program code. | |||
*[https://www.ni.com/docs/en-US/bundle/labview/page/labview-style-checklist.html LabVIEW Style Checklist] | |||
*[https://wiki.dqmh.org/dqmh/styleguide DQMH Queued Message Handler Style Guide] | |||
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. | ||
[[Category:LabVIEW fundamentals]] | [[Category:LabVIEW fundamentals]] | ||
Latest revision as of 15:17, 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:
Additionally, there are checklists and style guides that contain more detail when ensuring consistency of style in LabVIEW program code.
These guidelines in programming style are important and can be check through automated inspection using the VI Analyzer toolkit.