public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/50645] old issue - deprecated conversion from string to char*
Date: Fri, 07 Oct 2011 00:41:00 -0000	[thread overview]
Message-ID: <bug-50645-4-LknufNL5xO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50645-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50645

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-10-07 00:41:25 UTC ---
(In reply to comment #0)
> 
> If I declare:
> 
> const char    *DowNames[] = {
>         "Sun", "Mon", "Tue", "Wed", "Thu", "Fri", "Sat", "Sun",
>         NULL
>     };
> 
> as just char* instead of const char*, YES I WOULD LIKE TO GET A WARNING.

So you want a warning if non-const pointers point to const data. Makes sense.

> HOWEVER, if I have a function:
> 
> myfunction(char *buf) {}
> 
> I'd like to be able to call it like this 
> 
> myfunction("hello world") 
> 
> ... WITH NO 'deprecated conversion from string to char*' WARNING

So you don't want a warning if a non-const pointer points to const data.
Huh?  How is that different from the earlier case.

> because char* as a parameter should be able to take a string as an argument --
> this makes sense.

Why?  If a function takes char* it means it can change the contents of the char
or chars at that address, why is a warning not appropriate if you call it with
an argument that might cause a runtime error if the function changes the data?

> It's annoying to have to cast (char*)"hello world" every place in code, as
> programmers always used to use, simply "hello world". (i know an option is to
> change the warning level -- but that has other issues.)

Or, if your function really doesn't change the data, you could always fix its
signature to be myfunction(const char*).

Or use C, instead of C++ (you do realise the warning you're complaining about
is a C++ warning, not a C one, right?)

> PLEASE UNDEPRECATE!  (Keep things simple, keep backward compatibility, as the
> old-school way is often best, designed that way for simplicity!)

That conversion is deprecated by the C++ standard, GCC cannot un-deprecate it.
Talk to the C++ committee (who will tell you to stop living in the 1970s and
get over it, type safety is a good thing.)


  parent reply	other threads:[~2011-10-07  0:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07  0:11 [Bug c/50645] New: " mike.c at rocketime dot com
2011-10-07  0:35 ` [Bug c/50645] " mike.c at rocketime dot com
2011-10-07  0:38 ` pinskia at gcc dot gnu.org
2011-10-07  0:41 ` redi at gcc dot gnu.org [this message]
2011-10-07  0:44 ` redi at gcc dot gnu.org
2011-10-07  1:11 ` redi at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-50645-4-LknufNL5xO@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).