遵循以下最佳实践的项目将能够自愿的自我认证,并显示他们已经实现了核心基础设施计划(OpenSSF)徽章。 显示详细资料
[](https://www.bestpractices.dev/projects/971)
<a href="https://www.bestpractices.dev/projects/971"><img src="https://www.bestpractices.dev/projects/971/badge"></a>
The GNU Astronomy Utilities (Gnuastro) is an official GNU package consisting of various programs and library functions for the manipulation and analysis of astronomical data. All the programs share the same basic command-line user interface for the comfort of both the users and developers. Gnuastro is written to comply fully with the GNU coding standards so it integrates finely with the GNU/Linux operating system. This also enables astronomers to expect a fully familiar experience in the source code, building, installing and command-line user interaction that they have seen in all the other GNU software that they use.
The Gnuastro manual has a complete section devoted to "Coding conventions" (https://www.gnu.org/software/gnuastro/manual/html_node/Coding-conventions.html). Generally, there is a full "Developing" chapter in the manual (https://www.gnu.org/software/gnuastro/manual/html_node/Developing.html) which is only devoted to guidelines for the developers
For bugs: http://savannah.gnu.org/bugs/?group=gnuastro For tasks: http://savannah.gnu.org/task/?group=gnuastro
Gnuastro uses the standard GNU Build system (./configure',make', make check') which also includesmake install' and `make install'.
./configure',
make check') which also includes
In the "Developing" chapter of the Gnuastro book, we try to discuss this with the developers or those interested: https://www.gnu.org/software/gnuastro/manual/html_node/Test-scripts.html
That is correct, For example this commit: http://git.savannah.gnu.org/cgit/gnuastro.git/commit/?id=195fae5be4f3 where several compiler warning were reported to us and we immediately addressed them.
警告:需要更长的理由。
We haven't implemented a static code analyzer yer.
We use Valgrind for checking the dynamic memory allocations in Gnuastro.
后退