David does code in an older style and that can look odd to newer programmers, but the newer styles look verbose to older programmers. I tend to use every const declaration possible, etc., so that the compiler will show me more coding errors and it has frustrated me that the codec2 code doesn't do the same, but I'm sure the verbosity would drive some people crazy. Newer code uses something like Doxygen to self-document, which would be a good project to add.
Regarding how open the church is, when you do close-to-the-metal coding, real-time, or have to handle timing and latency issues, you need a greater skill level. And in general I'd expect anyone to approach a project of any level to have a really good look at the way things work before approaching the developers. I can't overstress the importance of reading other programer's code in the Open Source community. I am in the unenviable position of having to clean up after commercial programmers who code for consumer and B-to-B products, usually when they infringe copyright and I have to help them to remedy the infringement. These are companies like LG and Google, and vendors to banks, Wall Street, and government. We can't pretend their standards are higher. The most glaring lack is regarding security - most folks just haven't spent enough time in the shoes of an operating system programmer to understand it. But this also comes out in the way they deal with any systems programming issue.
------------------------------------------------------------------------------
_______________________________________________ Freetel-codec2 mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freetel-codec2
