ID: Q117386
1.00 1.50 WINDOWS kbtool kbbuglist
The information in this article applies to:
- Microsoft Visual C++ for Windows, versions 1.0 and 1.5
The linker generates the following error message when you export a class that contains a user-defined conversion function (conversion operator):
error L2022: __aab: export undefined
Exporting the conversion function individually also causes the linker to
generate the above error message.
The compiler generates incorrect code for the function that implicitly uses the conversion function. LINK is unable to resolve the export.
To correct the error, rewrite the function that implicitly calls the conversion function. For the sample code in the "MORE INFORMATION" section below, use one of the following workarounds:
Text Mytext;
String temp = String( Mytext );
}
-or-
Text Mytext;
String temp;
temp = Mytext;
}
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
This is not a problem in Visual C++, 32-bit Edition.
The problem only occurs if the conversion function switches from one class to a user-defined class. The problem does not occur if the class is not a user-defined class. For example:
Class MyClass
{
_export operator int(); // OK
}
/* Compile options needed: none
*/
class __export String // A user defined class
{
public :
String(){}; // Constructor
};
class __export Text
{
public:
Text(){} // Constructor
operator String(); // User defined conversion function
private:
String m_text; // Data member
};
Text::operator String() // Function definition
{
return m_text;
}
void __export Global_Function()
{
Text mytext;
String temp = mytext; // L2022 Error
}
Additional reference words: 1.00 1.50 8.00 8.00c
KBCategory: kbtool kbbuglist
KBSubcategory: CPPIss
Keywords : kb16bitonly
Last Reviewed: July 23, 1997