conversion from const char* to const wxString is ambiguous

[Paul Koning]

>>>>> "Alfredo" == Alfredo Cole <alfredo at acyc.com> writes:

 Alfredo> Hi: I'm using wxGTK 2.6.3 as it comes with SUSE 10.2. I was
 Alfredo> using SUSE 9.3 and wxGTK 2.4.2 before and never saw this
 Alfredo> message. My project has over 400 source files and are
 Alfredo> getting all kinds of weird error messages. Needless to say,
 Alfredo> it compiled Ok previously. Is there a place where I can read
 Alfredo> about converting from 2.4.2 to 2.6.3, and gcc 3 to gcc 4? I
 Alfredo> think this may be the problem but I am not sure.

The short answer is that GCC 3.4 (or 3.5, or 4.0?) changed the C++
parser.  The old parser allowed lots of constructs that violate the
ANSI C++ standard; the new one does a much better job of enforcing the
standard.

One side effect it that you may end up with code that now gets warning
or error messages.  Code that uses templates is particularly likely to
run into this, but there are probably other categories.  

The only solution is to make your code ANSI compliant.  You may need a
good C++ textbook for help with that.  (I used "C++ in a nutshell"
from O'Reilly for that.)

     paul