G++ would not allow this, take a look before it drives you nuts (example with QPalette)

lgeyer

You gave an opinion, someone else gave an opinion - so what's all this frenzy about here?
You decided to post on a public forum, so

you should be able to ignore or report posts you find improper or
you should not post on public forums

There is a broad consensuns here at the QDN that rude behaviour and personal insults are not tolerated. Period.

As to your initial post: The compiler warning has been surpressed by an explicit cast. This is the behaviour I would expect. There is a reason const casts should be rarely used.

As to your suggestion: Rejected. The API already provides the requested functionality and the saving of two lines of code (at best) does not justify this redundancy. This would violate Qts API design principles. As already suggested I would create an inline function.

However, feel free to add the requested functionality and submit a merge request. This is how such discussions are usually solved here.

? Offline

->Volker
-> Lukas Geyer

Insults ? For a "Got it ?".
Our defintions of this word must be very different.
As for my "rude" behaviour, to quote you Mr Geyer,
it was triggered by the patronizing tone of most
answers to my posts. However I must admit your
last reply' s technical remarks (const_cast and API
design principles)make perfect sense.

I just had a peek at your profile:
Congratulaions for having, and for so long, contributed
to such a great toolkit.

? Offline

->peppe

Sorry for my unbecoming remark.

-> Tobias Hunger (with some delay)

Mr Hunger,

I a am an Assembly language x64, APL and C programmer
but a newcomer to C++ and its design philosophy.
As for GUI toolkits, the only one I knew about was GTK +.
I dropped it because of its implementation of signals I don' t
like, to the say the least.
So, I was very surprised by g++ (legitimate) reaction
to my attempt to call setColor through a constant reference
to a QPalette. Realizing shortly after that it made sense but
considering I had the "right" to cast this thing. Well, since
g++ stopped complaining I thought it might be appropriate
to inform those likely to run across the same kind of problem
that my trick worked. It was my sole purpose. Now, it does
infringe QT design philosophy as you and Mr Geyer, among
others, pointed out.

Congratulations for your continuing contribution to Qt.

mgran

Just (pa)trolling past this thread and it's encouraging to see that things are sort of sorted :)

goetz

Hi Quicksort,

[quote author="Quicksort" date="1317767499"]
I a am an Assembly language x64, APL and C programmer
but a newcomer to C++ and its design philosophy.
[/quote]

that's an important information which will put your first post in a completely different context. I'm pretty sure, everyone here thought you were quite familiar with C++ and the concepts. So some of the answers could have looked a bit weird to you.

Anyways, if you want to read some good stuff on C++ features, I can recommend you the "C++ FAQs":http://www.parashift.com/c++-faq-lite - it's always a good inspiration. Not to forget to leave behind many of the concepts of assembly language or C (including casts!) when switching to C++ :-)

? Offline

Thank you for your friendly post, Volker.
I will take a close look at these FAQs, I have a lot to learn...
Now, you might be, the case being, interested in Dr Agner Fog' s
manual about C++ optimization (from a programmer viewpoint,
it' s not about compiler writing).
I encourage everyone to visit his great website http://www.agner.org/.
You will find there various manuals and (free) software packages.
This man has an incredible knowledge of microprocessor architectures
and assembly language optimization. I owe him so much.

Cheers.