3 ms·
This so called CCAN is missing the most important point of CPAN: Minimum code quality in terms, that code must compile same way, install same way, test itself s
by kephra 13y ago
This so called CCAN is missing the most important point of CPAN: Minimum code quality in terms, that code must compile same way, install same way, test itself same way, and have a documentation that describes how to use it. In addition CPAN provides extended code quality by PAUSE and CPAN testers.
- berntb 13y agoI think most of that needs to come from bottom-up, that is from contributors. Let us hope it generates a good community. (A working "CCAN testers" would be wonderful for C code. People would want to upload stuff just to get compilation/test errors on different O/S versions, with small-/big-endian architectures, etc, etc.) Edit: Grammar.
- RustyRussell 13y agoHi Kephra, Perhaps the site isn't clear, but this all exists. 1) All CCAN modules compile with by providing a config.h and compiling * .c (if any). Metadata (eg. linking requirements, other modules) is in the _info file. 2) These are not libraries, though they can be compiled like that of course. So install is outside scope. 3) Testing is done in the modules' test subdir. compile-ok* .c and compile-fail* .c tests are what you'd expect. run* .c are compile-standalone-and-execute-with-0 status tests. api* .c are compile-with-module-and-execute tests. 4) The documentation standard is in the form of parseable but human-readable comments in the header files and _info. The ccanlint tool will do most of this for you. I hope that helps clarify.