Stan Lippman's BLogC++/CLIThe String Literal Returns- December 8, 2004 In the last entry, I celebrated what I felt was an elegant solution to the problem of the string literal in the context of overload function resolution. But it turns out there is another area in which the string literal proves problematic. Who would have thought such a foobar kind of entity could cause so much trouble It's these kinds of ambushes that makes the extension of a language so unpredictable. So, here's the problem. ...http://blogs.msdn.com/slippman/archive/2004/12/08/278163.aspx The Type of a String Literal Revisited ...- December 4, 2004 In the course of these entries, I have twice addressed the issue of the type of a string literal under C++CLI -- in particular when resolving an overloaded function call. The issue is illustrated in the following example, public ref class R public: void foo( System::String ); (1) void foo( std::string ); (2) void foo( const char ); (3) ; void bar( R r ) which one r->foo( "Pooh" ); In the original.http://blogs.msdn.com/slippman/archive/2004/12/04/275069.aspx |