LabWindows/CVI Idea Exchange

About LabWindows/CVI Idea Exchange

Do you have a feature idea for how to improve LabWindows/CVI? Submit and vote on ideas now!
  1. Browse by label or search in the LabWindows/CVI Idea Exchange to see if your idea has previously been submitted. If your idea exists, be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click New Idea to submit a product idea. You should submit a separate post for each idea. Watch as the community gives your idea kudos and adds their input.
  3. Give kudos to other ideas that you would like to see implemented!
  4. NI R&D will review ideas that have been submitted and update the status.

Note: the LabWindows/CVI Idea Exchange is not the appropriate forum to submit technical support questions.

The LabWindows/CVI R&D team is committed to reviewing every idea submitted via the LabWindows/CVI Idea Exchange. However, we cannot guarantee the implementation of any LabWindows/CVI Idea Exchange submission.

Showing results for 
Search instead for 
Did you mean: 

Add full C++ support

I add this new idea based on the info on this thread.

I know that this idea is almost the same, but the basic reason is quite different.

 

I think that C++ offers much more flexibility for the development and it is a much more powerful approach for the future.

Now CVI uses CLANG/LLVM compiler, that is a C/C++ compiler.

But, as written by Luis from NI

Supporting C++ entails far more than just the compiler. For example: the standard C++ library (including templates, etc...), the APIs of all the standard CVI libraries, the source editor (auto-indentation, coloring, etc...), code-generation from the various wizards, memory runtime checking, debugging, etc... so, even though the compiler does support it, for all of CVI to support C++ is still an extremely large undertaking that has to be weighed against other, competing work that's going into CVI.

 

 

3 Comments
Wolfgang
N/A

I have a comment Smiley Tongue

 

In my opinion this suggestion should address Measurement Studio, where APIs, libraries, source editor all are available - the 'only' change required to me seems that Measurement Studio would need to support LLVM.

 

Of course it would be nice to have 'everything' in one package, but we all know that reality is different and it was much effort to bring LLVM to CVI, it took 4 years (CVI2013 and CVI2015) and as a result no other suggestions could be implemented.

 

Given this reality I really prefer having improved tools for C instead. 

 

But I could support the idea of re-uniting CVI and Measurement Studio if this would double the NI resources available for CVI++ Smiley Happy

vix
N/A
Honestly speaking, it's not 100% clear to me what is the basic difference between between Measurement Studio and CVI. I think that CVI is Measurement Studio plus an IDE developed by NI. With MS you must use a third party IDE. I think (and I hope) that MS and CVI share the same underlying libraries.
AlejandroR
N/A

Including C++ support would probably be too much work considering that there already are successful C++ IDEs around which can be easily extended.

 

IMO there are two options:

EITHER make the change to eclipse OR optimize MeasurementStudio so we can just open CVI Projects without much conversion hassle.

 

EDIT: Also, have a look at this as it covers a similar topic.