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
 Bug with create declaration
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

MrDoomMaster
Tomato Guru

251 Posts

Posted - Jul 31 2012 :  12:32:36 PM  Show Profile  Reply with Quote
I have the following class:

namespace foo {
class bar
{
public:
  void dostuff();
};

} // namespace foo


and in my CPP, I have the following:

namespace foo {

void bar::dostuff() {}

} // namespace foo


Now let's say I am in the CPP and I add a new function definition to the class without putting its declaration first:


namespace foo {

void bar::dostuff() {}
void bar::otherstuff() {} // New function

} // namespace foo


I right click on this and create function declaration through VAX, and I get:

namespace foo {
class bar
{
public:
  void dostuff();
  void bar::otherstuff();
};

} // namespace foo


Visual Assist did not remove the "bar::" part from the declaration, as it should. I think it is getting confused because of the way I have the namespace wrapping everything.

Please fix this, I remember this bug from years ago and it's still here.

accord
Whole Tomato Software

United Kingdom
3277 Posts

Posted - Jul 31 2012 :  5:45:10 PM  Show Profile  Reply with Quote
I am seeing the same effect here. Thank you for the clear description.

case=6593
Go to Top of Page

MrDoomMaster
Tomato Guru

251 Posts

Posted - Oct 27 2012 :  2:09:02 PM  Show Profile  Reply with Quote
Any idea what build this will be fixed in? It doesn't seem to have been fixed with the latest release.
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
17256 Posts

Posted - Oct 29 2012 :  10:33:22 PM  Show Profile  Reply with Quote
Unfortunately I don't have an estimate on when this will be fixed. It is still on our list of things to fix.

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

MrDoomMaster
Tomato Guru

251 Posts

Posted - Oct 29 2012 :  11:23:53 PM  Show Profile  Reply with Quote
quote:
Originally posted by feline

Unfortunately I don't have an estimate on when this will be fixed. It is still on our list of things to fix.

Thanks! It's not a huge priority, I was just curious :)

Thanks for the great updates.
Go to Top of Page

MrDoomMaster
Tomato Guru

251 Posts

Posted - Apr 25 2013 :  11:15:02 PM  Show Profile  Reply with Quote
It's been nearly a year now since I reported this and no fix yet, a bit depressing to be honest :(
Go to Top of Page

accord
Whole Tomato Software

United Kingdom
3277 Posts

Posted - Apr 26 2013 :  4:29:47 PM  Show Profile  Reply with Quote
We have increased the priority of this bug for you, so it may be fixed before long if it's not a hard one to fix.

Edited by - accord on Apr 26 2013 4:31:31 PM
Go to Top of Page

support
Whole Tomato Software

5566 Posts

Posted - Jun 03 2013 :  2:02:52 PM  Show Profile  Reply with Quote
case=6593 is fixed in build 1940
Go to Top of Page

MrDoomMaster
Tomato Guru

251 Posts

Posted - Jun 28 2013 :  7:07:04 PM  Show Profile  Reply with Quote
Unfortunately this isn't fixed and I can still reproduce it.
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
17256 Posts

Posted - Jul 05 2013 :  12:19:18 PM  Show Profile  Reply with Quote
Apologies for this. Are you seeing this bug with the test code you started this thread with? Or are you only seeing this problem with more complex code in your main solution?

Which IDE and version of VA are you using?

Are you using macros to generate your namespace?

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

MrDoomMaster
Tomato Guru

251 Posts

Posted - Jul 24 2013 :  4:00:13 PM  Show Profile  Reply with Quote
quote:
Originally posted by feline

Apologies for this. Are you seeing this bug with the test code you started this thread with? Or are you only seeing this problem with more complex code in your main solution?

Which IDE and version of VA are you using?

Are you using macros to generate your namespace?



Sorry for taking so long to respond. I have a consistently reproducible case. Basically if a class is within 2 or more nested namespaces, the issue still persists.

This is the same issue as I originally reported here, but instead of the 'class bar' being in one namespace, it's in two namespaces. I can also reproduce this when 'class bar' is within 3, 4, or even 5 namespaces:

namespace foo {
namespace bar {

class Test
{
public:
    void func1();
    void func2();
    void Test::func3(); // This one was created by "Create Declaration"
};

}}


The fix for this should handle ANY level of namespaces.
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
17256 Posts

Posted - Jul 25 2013 :  3:31:30 PM  Show Profile  Reply with Quote
Apologies for not fully fixing this the first time round. I have re-opened:

case=6593

and I have included an example of this effect using 5 nested namespaces, so we have a good test case in hand.

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

support
Whole Tomato Software

5566 Posts

Posted - Sep 25 2013 :  4:37:04 PM  Show Profile  Reply with Quote
case=6593 is fixed in build 2001.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2019 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000