Re: Const qualifier conversion warnings
Re: Const qualifier conversion warnings
- Subject: Re: Const qualifier conversion warnings
- From: Justin Walker <email@hidden>
- Date: Fri, 3 Jun 2005 12:36:06 -0700
On Jun 3, 2005, at 12:22, Theodore H. Smith wrote:
[snip]
I see a compilers job as to be making my job easier. I know when code
is correct or not, and I know that that code is correct at least as
far as constness goes, so I'd like to be able to tell the compiler to
not make my job harder by complaining about stuff that's fine.
The compiler is doing its job correctly. Your problem is that your
mass of valid, working code is no longer valid by the definition of C++
(at least, as interpreted by the compiler in question). Each version
of g++ moves closer to a somewhat moving target, the C++ standard.
I understand your problem, having been dealing with code written in the
last century, with compilers written in this century :-}. The problem
gets even worse when you are dealing with large libraries over which
you have little control. For this particular case (call discards
qualifiers), I have yet to find a good answer.
Regards,
Justin
--
Justin C. Walker, Curmudgeon-At-Large
Institute for General Semantics
--------
When LuteFisk is outlawed,
Only outlaws will have LuteFisk
--------
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden