| Author |
 Topic  |
|
|
enigma
Senior Member
49 Posts |
 Posted - Jun 06 2007 : 9:25:50 PM
|
In vs.net 2003, type in these two methods:
public void MethodA(double aa, double bb)
{
}
public void MethodA(double aa)
{
}
place your cursor at the second method and choose "change signature", you will find that the intellisense suggests this:
public void MethodA(double aa, double bb)
But really, it should suggest MethodA(double aa)
I'm using build 1557 |
http://itscommonsensestupid.blogspot.com/ |
|
|
feline
Whole Tomato Software
United Kingdom
19023 Posts |
Posted - Jun 07 2007 : 11:27:38 AM
|
Currently this is a known limitation:
case=2164
The same problem shows up with alt-g when jumping to an overloaded function. Currently VA does not understand which overload you are calling. Default parameters complicate this, so we cannot even rely on something as simple as counting the parameters to help work this out. |
zen is the art of being at one with the two'ness |
 |
|
|
pvercello
New Member
8 Posts |
Posted - Jan 22 2008 : 4:39:14 PM
|
An unfortunate side effect of this is that if you use the feature, it can end up changing signature of the wrong version of the method, which can cause subtle bugs that aren't always caught by the compiler, depending on the properties of the types. It'd be nice if it could at least disable the feature when it detects overloaded methods in a class, even if it can't distinguish them.
-pv
|
|
|
|
feline
Whole Tomato Software
United Kingdom
19023 Posts |
Posted - Jan 22 2008 : 7:42:24 PM
|
A very sensible suggestion, I have put in a case for this:
case=11717 |
zen is the art of being at one with the two'ness |
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Mar 30 2009 : 09:18:51 AM
|
| case=11717 is fixed in build 1721 |
Whole Tomato Software, Inc. |
|
|
| |
Topic |
|
Incorrect Change Signature for overloaded methods
