<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi,<div><br><div><div>On 11 Jan 2014, at 15:45, David van der Spoel <<a href="mailto:spoel@xray.bmc.uu.se">spoel@xray.bmc.uu.se</a>> wrote:</div><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br>For the future we should become even more stringent on new code. I<span class="Apple-converted-space"> </span><br>propose to also prevent new C code from going into the mdrun part of the<span class="Apple-converted-space"> </span><br>code, at least past release of 5.0. Only by forcing all developers to<span class="Apple-converted-space"> </span><br>make the switch can we get a broader developer base for future coding.<br></div></blockquote><br></div></div><div>When it comes to new modules I fully agree. We should also get better at replacing old modules (well, starting with modularizing stuff), but I think it’s better to keep _old_ code and patches to it C so we properly clean up and modularize as we advance, rather than having a gigantic unstructured mix of C and C++ code in all files.</div><div><br></div><div>Cheers,</div><div><br></div><div>Erik</div></body></html>