Should I put many functions into one file? Or, more or less, one function per file?

Question

I love to organize my code, so ideally I want one class per file or, when I have non-member functions, one function per file.

The reasons are:

1. When

Answer 1

I also tried to split files in a function per file, but it had some drawbacks. Sometimes functions tend to get larger than they need to (you don't want to add a new .c file every time) unless you are diligent about refactoring your code (I am not).

Currently I put one to three functions in a .c file and group all the .c files for a functionality in a directory. For header files I have Funcionality.h and Subfunctionality.h so that I can include all the functions at once when needed or just a small utility function if the whole package is not needed.