Ways to show your co-programmers that some methods are not yet implemented in a class when programming in C++

Question

What approaches can you use when:

• you work with several (e.g. 1-3) other programmers over a small C++ project, you use a single repository
• you create a class,

Answer 1

You should either, just not commit the code, or better yet, commit it to a development branch so that it is at least off your machine in case of catastrophic failure of your box.

This is what I do at work with my git repo. I push my work at the end of the day to a remote repo (not the master branch). My coworker is aware that these branches are super duper unstable and not to be touched with a ten foot pole unless he really likes to have broken branches.

Git is super handy for this situation as is, I imagine, other dvcs with cheap branching. Doing this in SVN or worse yet CVS would mean pain and suffering.