On 2016-02-24 06:52-0500 Hazen Babcock wrote: [Alan] >> Anyhow, I am convinced by my above estimate that the propagation part >> of the work will require similar effort to the rest of the project, I >> do like the simplicity of the return code method that has proved to be >> so useful in the ephcom case, and I think the above testing method >> will insure the whole effort will give reliable return code results. >> Also, I think we are talking a few weeks of one-man effort rather than >> months to get this done completely. Therefore, I stand willing (early >> in the next release cycle) to make this happen. Of course, many hands >> make light work so I would welcome some help with this project. > [Hazen] > I agree with your time estimate. I also agree that the return codes > approach is the right way to do it, and even if it does end up taking > longer than expected it will be more than worth the effort. So I'd be > happy to help. I guess we'd start with a header file containing a list > of possible error codes, and then split up the editing of the various > files in the src/ directory between those who volunteer?
Hi Hazen: I think that would be a good approach, and thanks very much for volunteering to help with this important project. Note, I have recently argued for an immediate exit approach for memory allocation errors which would vastly simplify what we had to do. But if you feel strongly that even those errors that only appear for emergency conditions should be included in the error reporting system, I would be willing to go along with that. Also, as noted before I won't have time to work on this project until the current release is out the door (still something like a month or so away). However, if you do have time to work on this now, please just go ahead on a private topic branch rather than waiting for me. Right after the current release is out the door you could push your matured topic branch to master or else if it is not matured by then, I would be willing and highly motivated to add a lot of energy to the project at that stage with the goal of getting this topic matured quickly so we can push it to master not too long after the current release is done. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
