Comments on: One good thing in Objective-C

By: Atif

Atif — Tue, 19 Apr 2011 15:19:47 +0000

Another way to do just that, is to make the methods file static functions if they are truly private, and not publish them in the header, but at the top of the cpp file.

Of course, these functions are no longer member functions, so public member functions have to pass them the references to class state.

By: RFC: Improving Qt’s properties. | Technical Difficulties

RFC: Improving Qt’s properties. | Technical Difficulties — Thu, 01 Jul 2010 16:40:53 +0000

[...] look like from stone age. Objective-C has some nice features as well, one I mentioned in my previous post, which Qt already solves rather nicely and in a better way as one of the commenter pointed out. [...]

By: digitalSurgeon

digitalSurgeon — Tue, 13 Apr 2010 09:38:45 +0000

@Robin, I am familiar with that approach ( thanks to Qt ). But I think this could be added to the next C++ language update. Do you see any thing wrong with it ? I mean not declaring private functions in the class declaration.

By: Robin Burchell

Robin Burchell — Fri, 09 Apr 2010 23:30:34 +0000

There is a solution to this, known as the PIMPL pattern (amongst other things)

Basically, you declare a pointer to a seperate class, and use that to store all your data members/methods you want private/etc. Qt is one big user of this pattern.

For example:

// .h

// forward declaration
class MyFooPrivate;

class MyFoo
{
void myBar();
private:
MyFooPrivate *d_ptr;
};

// cpp
class MyFooPrivate
{
void mooCow()
{
// make a moo noise
}
};

void MyFoo::myBar()
{
d_ptr->mooCow();

// do other stuff
}