<div dir="ltr">I would also advocate that we keep a public API (and can help maintain it if needed--let me know). I think a Python API will be super-useful and would become the most common means of scripting Gromacs. Nonetheless, having a C/C++ API, even if not a super-slick one, is quite helpful as Christoph mentions. I've used it in a number of pieces of un-released code (things not in the Gromacs source tree that build with Gromacs). One could argue that un-released code could hack in hooks, but that's kind of ugly.<div>
<br></div><div><div class="gmail_extra">What are the major reasons to remove the API? Ugliness, install bloat, the fact that every feature has non-zero maintenance effort? Other things I'm missing?</div><div class="gmail_extra">
<br></div><div class="gmail_extra">Thanks,</div><div class="gmail_extra">--Peter<br clear="all"><div><br>----------------------------------------------------------------------<br>Peter Kasson, MD, PhD<br>Assistant Professor<br>
Departments of Molecular Physiology and Biological Physics<br>and of Biomedical Engineering<br>University of Virginia<br></div>
<br></div></div></div>