Re: MFC Message Handling

From:

Goran <goran.pusic@gmail.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Wed, 25 Nov 2009 04:04:15 -0800 (PST)

Message-ID:

<cefd8c3a-d9d3-4ec1-997e-0d43cb913b2d@f16g2000yqm.googlegroups.com>

On Nov 25, 9:52 am, rahul <hyrahu...@gmail.com> wrote:

In MFC Generally when we Override Message Handling function by a class
then we call base class function at the end like,
return CPropertySheet::PreTranslateMessage(pMsg);

how this is valid??
If PreTranslateMessage() is not static function then how can we call
it by this way (i.e. ClassName::FunctionName)??

(Not at all MFC question, BTW. Try http://groups.google.com/group/comp.lang=
..c++.moderated/topics
for more involved crowd).

I would guess the most important reason that this is allowed really is
inheritance.

That said, why you think it's important that language prevents you
from using fully-qualified function name? It's the same call, just
longer to type (but, important with inheritance).

Note that you can also do:

class Type
{
public:
static void StaticFunc() {}
void Func() {}
};

Type var;
var.StaticFunc(); // !!! works not with class name, but class instance
var.Type::Func(); // !!! works, too

Goran.