Excellent, thanks guys,
On 7 Apr 2009, at 03:21, Ross Finlayson wrote:
There are functions, but also "char *" variables like that :
char * example;
example = "const string";
please find a list of the warnings attached (using today release).
OK, I've now installed a new version (2009.04.07) o
There are functions, but also "char *" variables like that :
char * example;
example = "const string";
please find a list of the warnings attached (using today release).
OK, I've now installed a new version (2009.04.07) of the code that
fixes most of these.
Thanks for the help.
--
Ross Finl
Quoting Ross Finlayson :
> Just let me know the functions (and parameters) for which this is an
> issue (there probably aren't many of them), and I'll fix them.
Hi,
There are functions, but also "char *" variables like that :
char * example;
example = "const string";
please find a list of the
Working on a idea for a project and compiled up live on my Fedora
10 box, with gcc version 4.3.2
Noticed a tone of warnings such as ...
"warning: deprecated conversion from string constant to 'char*'"
This is from passing a "string" to a function that's expecting a
char*. Can be cleaned up in
Looking back at the archives, I see that Erik Hovland submitted a big
patch for something similar.
On 3 Apr 2009, at 10:13, Glen Gray wrote:
Hey Guys,
Working on a idea for a project and compiled up live on my Fedora 10
box, with gcc version 4.3.2
Noticed a tone of warnings such as ...
Hey Guys,
Working on a idea for a project and compiled up live on my Fedora 10
box, with gcc version 4.3.2
Noticed a tone of warnings such as ...
"warning: deprecated conversion from string constant to ‘char*’"
This is from passing a "string" to a function that's expecting a
char*. Can be
