|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools |
Rating:
|
Display Modes |
|
#23
|
||||
|
||||
|
Re: Teams happy with Wind River Workbench?
With half of our programming team having C/C++ experience and the other half being rookies, it may have made more sense to have used WRWB instead of LabView. However, the powers that be believe that C/C++ support is going to be phased out (personally,I don't feel that this would happen anytime soon, if ever) so this year we used NI LabView. This caused more than a few grumbles from veterans (myself included). I still have a few complaints about the amount of time it takes to implement simple operations in LabView vs the same operations in C/C++ (i.e. assigning the sum of two numbers to a variable), however, the connect-the-dots sort of layout makes it easier to read and document VIs than .cpp/.h files (not that half of our code is documented...
). |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Obscure Wind River Workbench Problem | {td} | C/C++ | 16 | 01-21-2010 10:11 AM |
| Wind River Printing from cRio | Mr.Macdonald | C/C++ | 6 | 01-12-2009 08:42 PM |
| Wind River header issues | dpeterson3 | C/C++ | 6 | 01-11-2009 06:17 PM |
| Wind River Help | BenB | Programming | 3 | 01-02-2009 09:42 PM |
| Open Wind River | excel2474 | Programming | 12 | 12-31-2008 05:36 PM |