@codebrainz I here your concerns, but the fact it doesn't conflict and has had 3 reports (now 4) about it seem a reasonable enough reason to distribute it to me. Especially as it's fairly trivial to support.
The previous reports were just about adding the extensions to `filetype_extensions.conf` so the files would get detected as the proper C/C++ filetype that they are. It wasn't until @elextr [suggested a custom filetype](https://github.com/geany/geany/pull/1328#issuecomment-264328288) in passing that this became about adding a 2nd C/C++ filetype.