Article ID: 116240 - Last Review: July 5, 2005 - Revision: 2.1 FIX: Compiler Errors Initializing const Reference to an ArrayThis article was previously published under Q116240 On This PageSYMPTOMS
Initializing a "const" reference to an array with a "non-const" array
causes incorrect compiler errors to be generated. Two such errors are C2607
and C2561.
CAUSE
The C++ compiler does not properly handle initialization of a "const T&",
where T is an array. For example, you should be able to initialize a
variable of type "const float (&ref)[3][2]" with a variable of type "float
[3][2]", but the compiler does not handle this case. Furthermore,
interactions between const declarations and typedefs of arrays do not work
in all circumstances.
RESOLUTION
To work around the problem, either do not use the const specifier or add
explicit casts to the appropriate const types.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This problem was corrected in Microsoft Visual C++ .NET. MORE INFORMATION
The sample code below demonstrates the problem. Compiling it yields at
least one of the following error messages:
error C2607: 'initializing' : cannot implicitly convert a 'int [3][2]'
to a 'int __near &[3][2]' that is not const error C2561: 'getMtx' : function must return a value Note: Simply removing the const specifier from the getMtx function's return type eliminates the problem. Sample CodeAPPLIES TO
| Article Translations
|

Back to the top
