Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Technical Support
 Code Inspection - Suggestion on destructors fail

You must be registered to post a reply.
Click here to register.

Screensize:
UserName:
Password:
Format: BoldItalicizeUnderlineStrikethrough Align leftCenterAlign right Insert horizontal ruleUpload and insert imageInsert hyperlinkInsert email addressInsert codeInsert quoted textInsert listInsert Emoji
   
Message:

Forum code is on.
Html is off.

 
Check to subscribe to this topic.
   

T O P I C    R E V I E W
khb Posted - Apr 06 2017 : 4:46:11 PM
I'm using VS 2012 with VA 2212 in an MFC project and get the blue underline on destructor names, such as:
virtual ~CFoo() {}
Code Inspection suggests the option: Use '= default' and changes the code to:
virtual ~CFoo() = default;
However, this doesn't compile for me (error C2065 - undeclared identifier).
The default also gets a red wiggly underline and when I hover over it, then I am told that only =0 is allowed.

Am I doing something wrong or is this a bug?

Kind regards,
Marcus
5   L A T E S T    R E P L I E S    (Newest First)
sean Posted - Apr 26 2017 : 5:06:49 PM
case=105286 is fixed in build 2217.
khb Posted - Apr 07 2017 : 5:55:14 PM
Great! Thanks!

Kind regards,
Marcus
holedigger Posted - Apr 07 2017 : 12:42:39 PM
Some checks are already toolset dependent. For example, you won't be offered range-base loops in VS2010. They are also not offered if you are using a later IDE, but are building with VS2010 (VS2017 project, with Platform Toolset = v100)

We'll update the "=default" check to only be active in VS2013 and later.
khb Posted - Apr 07 2017 : 12:25:12 PM
Well, I would prefer if non-supported features weren't suggested. I don't want to have any blue markings left after adapting everything I can. I understand that this might be difficult for custom compilers, but the VS own compiler should be correctly reflected, I think.

Kind regards,
Marcus
accord Posted - Apr 06 2017 : 6:34:37 PM
I was able to reproduce the problem which is that VS2012 update 5 doesn't support this C++ feature yet.

Would you prefer if fixes that aren't supported in a certain IDE wouldn't show up?

Although I'm not sure about the implementation since users can use any custom compiler, but I have put in a feature request for this:

case=105286

© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000