Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Technical Support
 C++11 =delete;
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

HarryStorbacka
New Member

4 Posts

Posted - Apr 04 2017 :  04:18:26 AM  Show Profile  Reply with Quote
Hi,

It seems constructors with C++11 �=delete� are still suggested in the function parameter popup. I'd expect them not to be listed there, since the constructor has explicitly been marked as deleted.

The constructor is defined as follows:

public:
MyClass(const MyClass& other) = delete;

Also constructors declared private are shown in the suggested parameters popup.

It would be nice to get a fix for this, because the illegal option often shows up first in the suggestions and requires navigating the menus each time to see the desired overloads parameters.

(This happens with the latest version of Visual Assist X)

feline
Whole Tomato Software

United Kingdom
18750 Posts

Posted - Apr 04 2017 :  10:11:06 AM  Show Profile  Reply with Quote
How are you using this class? Using VS2017 with VA 2212, I have the following test code:

class testDeleteConstructor
{
public:
	testDeleteConstructor(const testDeleteConstructor &rhs) = delete;
	void publicMember();
private:
	void privateMember();
};


void testUsingDelete()
{
	testDeleteConstructor testDel;
	testDel.|
}


when typing the dot, where the caret is marked, only the single public method for the class comes up in the listbox. I also have the setting:

VA Options -> Enhanced Listboxes -> Source of C/C++ content: Default Intellisense

zen is the art of being at one with the two'ness
Go to Top of Page

HarryStorbacka
New Member

4 Posts

Posted - Apr 05 2017 :  02:17:38 AM  Show Profile  Reply with Quote
I'm using visual studio 2013 update 4, and had also "Default Intellisense" as source of C/C++ content. I seem to get the same behavior also when using Visual Assist as the source of C/C++ content.

Good to know upgrading to vs2017 would fix this - Thanks!
Go to Top of Page

accord
Whole Tomato Software

United Kingdom
3287 Posts

Posted - Apr 05 2017 :  6:56:03 PM  Show Profile  Reply with Quote
This is what I'm seeing with VA 2212 and VS2013 update 5:



So either Update 5 makes the difference, or maybe the source code is not enough to repro the issue. Are you seeing the issue with this code on your computer?
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000