I would like to propose an idea for National Instruments to come up with a LabWindows CVI Peer Review Form. This form would be used to help a software programmer or engineer review someone else's code to ensure that they wrote the best code possible. It would provide a quick set of questions which the reviewers would need to look for in the code and then answer. The form would help ensure that the code was designed in a format that is easy-to-read, efficient, set up for all possible failures, is as organized as possible, etc. There could be separate sections based on the different types of files, whether it's a .uir, .c or .h file.
This idea is not new, since here is an example style checklist for LabView: https://zone.ni.com/reference/en-XX/help/371361L-01/lvdevconcepts/checklist/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi dstochel,
Thank you for your post. We are beginning development of a checklist similiar to LabVIEW's but for LabWindows/CVI development best practices. I'm sure it will go through many iterations so feel free to post any other thoughts of what you think should be included in the checklist.
Regards,
Collin Draughon
CVI Product Manager
National Instruments