This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c/49748] char * const * cannot be assigned to char const * const *


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

--- Comment #2 from Alain Knaff <gcc at misc dot lka.org.lu> 2011-07-14 17:38:59 UTC ---
Created attachment 24756
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24756
Test program for const warning bug

> the warning is correct, see http://c-faq.com/ansi/constmismatch.html

Thanks for this link. This does indeed confirm what I said, in much less words
than I needed. Moreover, it points out that the issue doesn't exist in C++.

However, it doesn't explain why the issue still present in C.

Any insights into this question?

If this is just to keep some paper-pushers happy, maybe we could keep the
current behavior as the default, but have a -W flag to make gcc mimic g++'s
behavior?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]