Comments on: Dependent bases, virtual functions, what does this call?

By: Andy Balaam

Andy Balaam — Tue, 21 Apr 2009 10:42:30 +0000

I could live with it if it were everywhere. It is the inconsistency that hurts me.

Python requires ’self.’, which is fine. Nice and explicit.

By: hashpling

hashpling — Tue, 21 Apr 2009 10:39:48 +0000

In which case you have a different set of problems and a diktat of ‘never use this->’ is an acceptable stance as the chances of them being in a situation where ‘this->’ is required and not understanding that the diktat can and should be ignored is vanishingly small. (Assuming that, like me, you are against unnecessary ‘this->’ which is often a sign of over-reliance on so-called ‘intellisense’.)

By: Andy Balaam

Andy Balaam — Tue, 21 Apr 2009 10:27:40 +0000

They always look blank.

By: hashpling

hashpling — Thu, 16 Apr 2009 18:47:41 +0000

Just ask them if they are accessing a member of a dependent base via an otherwise non-dependent expression. If they look blank, then it’s your queue to shout: “so why are you using ‘this->’?”.

I made this point on a SO question, but it’s so low down that no-one’s even bothered to downvote it.

By: Andy Balaam

Andy Balaam — Thu, 16 Apr 2009 09:08:14 +0000

So now I have to check very carefully before berating my colleagues for writing this->f() rather than just f().