[Qt-interest] 答复: capture screen

[Malyushytsky, Alex]

My main point was that I would not recommend anybody asking for help to change the style he is using.
In this not ideal world when every person is not our clone, everybody has some.
If you see valid C++ there is no point to enforce anybody to follow specific style.
The only exception would be the case when you deal with person who is working on the project where usage of specific style is enforced.

More of that such advices on mailing list tend to create a lot of out of topic discussions :)

Regards,
   Alex




-----Original Message-----
From: qt-interest-bounces at trolltech.com [mailto:qt-interest-bounces at trolltech.com] On Behalf Of Carsten Breuer
Sent: Tuesday, June 15, 2010 2:52 PM
To: Scott Aron Bloom; qt-interest at trolltech.com
Subject: Re: [Qt-interest] 答复: capture screen

Hi Scott,
hi all,

> However, when you have a function isHidden(), and inside the class you store a variable to store if its hidden, and you call it isHidden, without a prefix (f,s, m_ etc etc )
>
> Your function will have to look like..
> bool className::isHidden() const
> {
> return this->isHidden;
> }

Right. I like the microsoft approach very much and use it
for all my classes. So all members are prefixed with a m_.
All pointers are prefixed with m_p_.

> Frankly, I HATE in Qt where they do this, and it gets done a ton.. But Ive learned to live with it...
> In my view, The formatting of function names and methods should be different then member variables for just this reason.

Your are perfectly right. I have also my problems with
the QT naming conventions, because i use:

loadFromFile <-- Private or protected  function.
LoadFromFile <-- Public function.


Best Regards,



Carsten



>
> Scott

_______________________________________________
Qt-interest mailing list
Qt-interest at trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-interest


---------------------------------------------------------------------------------------------------
Weidlinger Associates, Inc. made the following annotations.

“This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. Thank you.”

“Please consider our environment before printing this email.”