comp.lang.c++

Ian Collins writes:
>There's nothing wrong with using lots of
>small function if they make the code clearer.

Once I had to write code in C++ that connects to
a database. There was no OOP-RDBMS mapper to be used.

I wrote an interface class for each table,
whose objects were intended to represent a table.
Possibly, there were »many« tables.

My supervisor did not like my approach.

Apparently, he measured code complexity by a count
(the more entities the more complexity, so many
classes seem to be very complex),
while I measured it by conceptual regularity
(one class per table is just one rule, so it is
very simple - and one can easily find the class
for a table, because they have the same name).