View Single Post
  #4   Spotlight this post!  
Unread 05-03-2014, 07:58
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Lint for LabView

I'm not sure if the VI Analyzer is included. To be honest, I rarely use it myself. It is great to help enforce coding conventions across a large team, but if I find that I've done something wrong, I generally just make a list of things to search for and plow through the code looking at the search results until I've verified things.

The simulator will almost certainly not match your robot's construction, but I don't think the robot will matter that much. The simulator will give your code a place to run, and the address checking for duplicate opens, bad names for the registry, etc, is done in WPILib. The FPGA and other elements have no knowledge of that. I don't know if I've seen the other thread about simulation issues. If you can, run your code there and see if it reports the same errors and gives you a place to track them down.

Greg McKaskle
Reply With Quote