View Single Post
  #19   Spotlight this post!  
Unread 23-04-2008, 20:56
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,756
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: Next Year's code

Quote:
Originally Posted by ExarKun666 View Post
So then Lab View is basically in C language, but with the addition of a graphical enviroment to test that programming on?
Not at all. The most obvious difference is that LV uses icons instead of words, but fundamentally, the big differences are that LV uses data flow for scheduling, and can therefore easily do multitasking at a pretty fine-grained level. Also, LV wires represent values, not references to values. This helps to avoid many side effects of procedural code.

Finally, LV encourages and rewards you making functions. Each function has a panel for entering values, and seeing results. These make very good modules for testing a portion of your algorithm "before" your robot is moving across the floor. You can test as many input sets and boundary conditions as you see fit. You can also have graphs and other useful indicators for looking at complex data.

So some of these are not language, but environment things, but these are fundamentally more important that the fact that LV is graphical instead of typed.

Greg McKaskle