Quote:
Originally Posted by Greg McKaskle
The biggest difference is that C++ is a very sequential procedural language. To do things in parallel is certainly possible, but is a bit more effort and a bit more dangerous.
Arrays in LV are autosizing, arrays in C++ aren't, but you can use vectors or other types that are more like LV arrays.
The debugging tools in LV and C++ are quite different.
The NI Vision libraries have both C and LV entry points, but the C++ WPILib doesn't do a very good job of bridging to the vision libraries. It seems to be a bit of work to get the camera image into an object that you can easily send to the CVI Vision functions.
And of course the obvious text is keyboard and graphics is mouse.
Greg McKaskle
|
All of these are very superficial differences,
To get through the parallelism issue you can easily use the Command-Based Template that WPI provide and you'll be good to go.
I would say one major thing in the decision is whether you have prior experience with C++ or Java, and if you're comfortable with it...
One of the things that really amazed me was the code deploying time difference between Java/C++ and LabView!
Besides, I really liked the organised OOP approach that WPI took with the Command-Based Template, and it's one of the thing that got me hooked, besides the fact that IMO LabView's messy and non-organised events order really took slowed down our work this year...