deprecated conversion from string constant to ‘wxChar*’ Topic is solved

[orbitcowboy]

Hello,

compiling my code with g++-4.3.3 on Ubuntu linux prints the following compiler warning:

Code: Select all

deprecated conversion from string constant to ‘wxChar*’

The code g++ warns about:

Code: Select all

    static  wxChar *Cmd[] = {wxT("some text"),NULL};

What i am doing wrong. Or, in other words, how to do it correctly?

Best regards

Orbitcowboy

[DavidHart]

Hi,

Change to static const wxChar*...

Regards,

David

[orbitcowboy]

Hi,

Change to static const wxChar*...

Regards,

David

Thank you, this works (the compiler warning is gone). But now i have another (strange) problem with wxExecute (http://docs.wxwidgets.org/stable/wx_pro ... #wxexecute)

I am using the second version of wxExecute

Code: Select all

long wxExecute(char **argv, int flags = wxEXEC_ASYNC, wxProcess *callback = NULL)

My compiler complains about the static const char *cmd[] = {...} list.

g++ says:

Code: Select all

‘void MyFrame::vDoAsyncExec(const wxString&)’:
../src/Frame.cpp:162: error: call of overloaded ‘wxExecute(const wxChar* [2], <anonymous enum>, wxSSHProcess<MyFrame>*&)’ is ambiguous
/usr/local/include/wx-2.8/wx/utils.h:353: note: candidates are: long int wxExecute(wxChar**, int, wxProcess*) <near match>
/usr/local/include/wx-2.8/wx/utils.h:355: note:                 long int wxExecute(const wxString&, int, wxProcess*) <near match>

removing the const makes my code compilable, but then the warning appears (see my first post)

What can i do?

Best regards

Orbitcowboy

[DavidHart]

Why not use a wxString instead? It's much easier.

[orbitcowboy]

Why not use a wxString instead? It's much easier.

Ok, this is a possibility. But not in my case. I would like to use this special version of wxExecute.

[DavidHart]

Ok, this is a possibility. But not in my case. I would like to use this special version of wxExecute

Hmm, then either ignore the warning (it's not dangerous, just annoying); or else add wxT("some text") to Cmd[0] dynamically, so you don't need the const (or the static, presumably).

[orbitcowboy]

Ok, this is a possibility. But not in my case. I would like to use this special version of wxExecute

Hmm, then either ignore the warning (it's not dangerous, just annoying); or else add wxT("some text") to Cmd[0] dynamically, so you don't need the const (or the static, presumably).

Thank you very much for your help!!

Best regards

Orbitcowboy