<p dir="ltr"><br>
On Jun 10, 2013 3:22 PM, "Erik Lindahl" <<a href="mailto:erik.lindahl@scilifelab.se">erik.lindahl@scilifelab.se</a>> wrote:<br>
><br>
> Hi,<br>
><br>
> On Jun 10, 2013, at 2:54 PM, Berk Hess <<a href="mailto:hess@kth.se">hess@kth.se</a>> wrote:<br>
> ><br>
> > In C++ we should certainly ditch the gmx_ prefix.<br>
> > In C as well in 5.0, as all C code should be hidden behind a C++ api, I suppose.<br>
><br>
> Note that I think we decided we should write out namespaces explicitly, so I assume one would actually write something like<br>
><br>
> gmx::module::submodule::procedure()<br>
><br>
> for parts that are C, I think it makes a lot of sense that the equivalent naming is<br>
><br>
> gmxModuleSubmoduleProcedure()<br>
><br>
> Whether we then use sub-namespaces or just separate modules with names, or even underscores instead of camelCames seems much less critical.<br>
><br>
> The advantage of both of the above alternative is that it is both clear where in the code this procedure or datatype is defined, and since we tend to use prodecure names like "UpdateXYZ()", I also think it's a whole lot clearer what we are updating in this case. When we use external libraries it is also very clear what names belong to Gromacs and which ones are external. Basically: can we find a scheme where functions and data-types are more self-documenting? I.e., I want it to be clearer what we are doing when we _use_ a datatype/function, rather than having to go to the declaration and hoping there is good documentation for a short acronym name there!</p>
<p dir="ltr">All seems good to me.</p>
<p dir="ltr">> And yes, that means I prefer a hypothetical long name like "gmxInteractionElectrostaticsPMEReciprocalEvaluate()" over "do_pme()". I can type both names in 3 letters and then hitting tab. The world moved away from 80-char-terminals some 30 years ago :-)</p>
<p dir="ltr">Hey, I used my first terminal thirty years ago, and it had 40 columns and 64k memory! It was a decade before I used a bigger one. :-) Also, if you have the brain cells to remember the unique three-character sequence of that function name, then you are clearly not working hard enough! But the principle is sound! :-) </p>
<p dir="ltr">Mark</p>
<p dir="ltr">><br>
><br>
> Cheers,<br>
><br>
> Erik<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> --<br>
> gmx-developers mailing list<br>
> <a href="mailto:gmx-developers@gromacs.org">gmx-developers@gromacs.org</a><br>
> <a href="http://lists.gromacs.org/mailman/listinfo/gmx-developers">http://lists.gromacs.org/mailman/listinfo/gmx-developers</a><br>
> Please don't post (un)subscribe requests to the list. Use the<br>
> www interface or send it to <a href="mailto:gmx-developers-request@gromacs.org">gmx-developers-request@gromacs.org</a>.<br>
</p>