<div dir="ltr"><div>All,</div><div><br></div><div>I apologize for reposting this post from yesterday, but it appears that gmail mangled the outgoing text, turning it into an attachment, making the text invisible on many platforms. Hope it works this time - and please ignore if you've already seen this.</div><div><br></div><div>/Thomas</div><div><br></div><div>Original post:</div><div><br></div><div><br></div><div>Janne,</div><div><br></div><div>First, I strongly object to being characterized as a “random rewriter”.</div><div><br></div><div>I have used proj since 1993, did my first (tiny) contribution to the code base in 1999, and I facilitated the inclusion of the etmerc, high precision transverse mercator code written by my colleague Karsten Engsager, in 2008.</div><div><br></div><div>It is correct that I have not touched the code base since then, but that does not turn me into a “random rewriter”. </div><div><br></div><div>Also, I described my intended work, and asked for comments and opinions on the proj mailing list more than a month ago. It attracted one comment, which was very much in favor of the work. It did not attract any comments from you.</div><div><br></div><div>Also, the pull request has been open since the beginning of april. Howard Butler, Even Rouault, and Micah Cochran have commented and given constructive feedback. I have seen no comments from you.</div><div><br></div><div>So all in all, you have had plenty of time to air your opinion. It would have been very helpful if you had done it a bit earlier than 2 months into the process. As a long term proj-list member, I know that you are a frequent and very helpful list contributor, so I have great respect for your experience and willingness to share it, and I believe you could have been a very helpful commenter and mentor for this work.</div><div><br></div><div><br></div><div>Second: In general I agree with your opinion of “not touching what works”.</div><div><br></div><div>However, what “works” is not easily definable - especially not in the long term.</div><div><br></div><div>Kristian Evers and I have turned to proj after having spent time updating trlib, the transformation system of the Danish national mapping agency (now SDFE, formerly GST, formerly KMS, formerly GI).</div><div><br></div><div>trlib originated as Algol code written around 1961, for the GIER system (a, for that time, medium sized computer, which was highly optimized for geodetic computations). The code survived and evolved through more than 5 decades following what was “current best practice” all along.</div><div><br></div><div>And the one “best practice” that has been prevalent through all these decades has been exactly the one you forward here.</div><div><br></div><div>The problem is that, while commendable for the medium term, for the long term “not touching what works” leads to kludge-upon-kludge, from bolting on additional functionality, while not touching existing code.</div><div><br></div><div>In the long term, the “not touching what works” dogma (NTWW in the following) leads to stale and unmaintainable code.</div><div><br></div><div>As an example, for trlib, one of the things we have removed during the last few years of code revision, is a complete user-space Virtual Menory mangagement system. It was evidently needed when added to the code around 1970, and left in due to NTWW when the code was migrated from Algol to C around 1980. And kept ever since, due to NTWW.</div><div><br></div><div>So our experience is very much that NTWW should be challenged now and then. Things change, and so do the hardware platforms the code is supposed to run on.</div><div><br></div><div>The proj.4 macro system reflects a development environment of Tektronix style, green phosphor 24x80 terminals, where saving vertical whitespace directly translated into a better general view, by having more context on screen at a time.</div><div><br></div><div>This is not the problem for modern coding tools on modern high-resolution displays. In today’s coding environment the proj internal macro system is a high barrier for entry: It makes it extremely hard for new coders to get productive.</div><div><br></div><div>If you look at the commit history, you will notice that new people enter the project in order to contribute one or two new projections that they need.</div><div><br></div><div>They do not stay to help evolving proj further. I hypothesize that this is at least partially because the macro system is convoluted and not at all C-like (e.g. leading to syntax highlighter blues).</div><div><br></div><div>My intention was to make the code less impenetrable, in order to make it more welcoming to new contributors. As you will see when you study the code, this has been done without touching the algorithmic flow. The procedure has been designed to enhance the clarity for human readers - not to touch the flow.</div><div><br></div><div>I suggest you read the description “A verbose justification for some highly intrusive code surgery” I wrote at the very beginning of this work, over at <a href="https://github.com/busstoptaktik/proj.4/blob/sdfe-refactor-macros--and-repair-generic-constructor-bug/src/PJ_minimal.c">https://github.com/busstoptaktik/proj.4/blob/sdfe-refactor-macros--and-repair-generic-constructor-bug/src/PJ_minimal.c</a>. Hopefully you will see that I have no intentions to break what works - but at medium time scale intervals, changing what works is necessary in order to keep things in shape.</div><div><br></div><div>regards</div><div>Thomas</div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">2016-05-20 16:19 GMT+02:00 <span dir="ltr"><<a href="mailto:support@mnspoint.com" target="_blank">support@mnspoint.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
Please! "if it works .. don't touch it" -- if you make "huge<br>
improvements" label the whole product something ELSE than Proj.4. and<br>
don't mix it with the stable version!<br>
We don't want to have random rewriters for the code since it does not<br>
add anything but more work for us! (... and lot of random errors and<br>
problems)<br>
<br>
Thanks! Janne.<br>
<br>
----------------------------------------<br>
<div class=""><div class="h5"><br>
Howard Butler kirjoitti 20.05.2016 16:50:<br>
> All,<br>
><br>
> I propose to add Thomas Knudsen and Kristian Evers to the Proj.4 team<br>
> with commit rights into the OSGeo/Proj.4 repository. They have been<br>
> leading a modernization effort in the Proj.4 package to improve<br>
> maintainability, reduce redundancy, and increase test coverage. Thomas<br>
> has also been a long time Proj.4 list member, and he has provided a<br>
> lot of experience and guidance on a number of coordinate system and<br>
> projection topics. Both have been software contributors in a project<br>
> that has been lacking them, and giving them full access will make it<br>
> more convenient for them to contribute.<br>
><br>
> I'll start with a +1.<br>
><br>
> Howard<br>
> _______________________________________________<br>
> Proj mailing list<br>
> <a href="mailto:Proj@lists.maptools.org">Proj@lists.maptools.org</a><br>
> <a href="http://lists.maptools.org/mailman/listinfo/proj" rel="noreferrer" target="_blank">http://lists.maptools.org/mailman/listinfo/proj</a><br>
<br>
</div></div><span class=""><font color="#888888">--<br>
MNS Support<br>
NNS Master Navigator Software<br>
Copyright © Sapper Oy<br>
<a href="http://www.mnspoint.com" rel="noreferrer" target="_blank">www.mnspoint.com</a><br>
<a href="mailto:support@mnspoint.com">support@mnspoint.com</a><br>
</font></span><div class=""><div class="h5">_______________________________________________<br>
Proj mailing list<br>
<a href="mailto:Proj@lists.maptools.org">Proj@lists.maptools.org</a><br>
<a href="http://lists.maptools.org/mailman/listinfo/proj" rel="noreferrer" target="_blank">http://lists.maptools.org/mailman/listinfo/proj</a></div></div></blockquote></div><br></div></div>