I was just looking at the source files of the Time library and it also defies the usual convention of c++ (as far as I am aware) of having your class defined in XYZ.h and the class functions defined in XYZ.cpp
It has the class definitions in TimeLib.h, the class functions implemented in Time.cpp and Time.h just includes TimeLib.h
Ultimately I don't give a rats as long as the library does what I want, but I would still like to understand why this sort of odd looking file naming is a bit a a 'thing' in Arduino libraries.
What would drive authors to have these sorts of arrangements over the stock standard c++ convention of XYZ.cpp and XYZ.h?
I could easily understand if the author had multiple classes defined in multiple XYZ.cpp/h file pairs and just wanted to include a single .h file in order to include all individual XYZ.h files in one line of code.
End of file
I don't 'get' why you would bother doing this?