Search

unable to match function definition by rhub

Closed
as Fixed Help for as Fixed

1
0
Sign in
to vote
Type: Bug
ID: 724362
Opened: 2/10/2012 6:44:10 AM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
0
Workaround(s)
0
User(s) can reproduce this bug
I am getting "unable to match function definition" when I try to compile attached code...

unable to match function definition to an existing declaration definition
'Action<T> *gear::core::ObjectController::createAction(Action<T>::CommandFunction,T *)'
existing declarations
'Action<T> *gear::core::ObjectController::createAction(Action<T>::CommandFunction,T *)'
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling version

Visual Studio 2010 SP1

Steps to reproduce

I have attached minimal "working sample".

Product Language

English

Operating System

Windows 7

Operating System Language

English

Actual results

unable to match function definition to an existing declaration definition
'Action<T> *gear::core::ObjectController::createAction(Action<T>::CommandFunction,T *)'
existing declarations
'Action<T> *gear::core::ObjectController::createAction(Action<T>::CommandFunction,T *)'

Expected results

.
File Attachments
File Name Submitted By Submitted On File Size  
main.cpp 2/10/2012 525 bytes
main.cpp 2/10/2012 525 bytes
Sign in to post a comment.
Posted by Microsoft on 2/14/2012 at 4:04 PM
Hi:
    A fix for this issue has been checked into the compiler sources. The fix should show up in the next release of Visual C++.

Xiang Fan
Visual C++ Team
Posted by MS-Moderator10 [Feedback Moderator] on 2/12/2012 at 5:57 PM
Thank you for submitting feedback on Visual Studio 2010 and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by MS-Moderator01 on 2/10/2012 at 7:43 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.