You must be registered to post a reply. Click here to register.
T O P I C R E V I E W
mmb
Posted - May 02 2007 : 5:09:57 PM I noticed today a small parse problem which I believe worked in older releases:
int (bla)(int x, int y) {}
While colored right, it is shown as
"bla)" in ListMethodsInCurrentFile and as "int (bla)(int x, int y)" in the context preview
However, the tooltip correctly shows the number of parameters.
(This construction protects bla from being replaced by the preprocessor, yes, again bad macro magic ;-)
5 L A T E S T R E P L I E S (Newest First)
feline
Posted - May 04 2007 : 09:44:48 AM I am seeing the same effect here. It seems that VA is rather confused by this, and I can see why:
case=6388
Do I want to ask why you have functions and macro's with the same name?
mmb
Posted - May 04 2007 : 05:48:32 AM feline: The problem seems be be more general and do not depends on parenthesis, see:
While the tooltip shows me the macro only, Alt-G jumps straigth to the function. Maybe I just don't understand the intention of Alt-G.
feline
Posted - May 03 2007 : 2:52:06 PM How easily can you reproduce this problem? using VS2005 and VA 1555 I have just tried the following code:
int (functionNameInBrackets)(int x, int y) { return 0; }
static void callFunctionInBrackets()
{
functionNameInBrackets(1, 2);
}
and alt-g works fine for me.
mmb
Posted - May 03 2007 : 1:04:31 PM Not sure about the old version. I found this because Alt-G did not jump to the paranthesed declaration and I believe it worked in older 14xx/15xx ones. The Alt-M was possibly broken all over the time, I use it rarely.
feline
Posted - May 03 2007 : 11:52:19 AM I am seeing the same effect here. Thank you for the clear description.
case=6366
I went back as far as VA 1301 and this failed in some form or other in all versions I checked. If you can remember which version it worked correctly in I can try testing it here.
