Future of teamwork plugin

[David Nolden]

Am Freitag, 6. Juli 2007 11:28:56 schrieb Andreas Pakulat:
> I think you got the wrong impression, at least for me its not solely
> about the advanced C++ stuff, its about unreadable code files, with
> #include's in the middle of a .cpp, with multiple classes in the same
> files (yes this might be judged as a personal preference, but I think
> its making it easier to understand code). On top of that the code will
> be unmaintained in the upcoming months and so far David said he will
> probably maintain it after SoC.

I don't think there is any includes in the middle of .cpp files. If you've 
seen it, then an individual case, and as such does not make the whole plugin 
unmaintainable.

There is only multiple classes in the same file when:
A) It is a few small helper-classes
B) It is a few classes that logically belong together and are not too big
C) It is a few small helper-classes plus one big main-class

In C++ you should ideally split the code into as many classes as it logically 
makes sense to keep things separate, and it's extremely unpractical to create 
a new file for each such class.

So that's a tradeoff between easy to read and easy to write, but I don't 
understand where this is a problem with features like code-navigation and 
jump-to-class at hand. By forcing a coder to create a new file for each 
class, you encourage him to create less classes, thereby you encourage him to 
less split his code into logical units, thereby you encourage him to write 
worse code.

greetings, David