>
>> I obviously don't have any idea of the size of ephcom, but Plplot
> must have thousands of internal function calls that would need the
> return value checking.
>
> I believe there are some 300 functions in our public and private API,
> and not all of those will be affected by this (because there are no
> error conditions they generate or they need to propagate). So I would
> estimate "hundreds" of functions rather than "thousands" would be
> touched by this propagation effort.
>
> Also, I think the editing task for propagating return codes would be a
> similar effort to the editing task for replacing the call to plexit by
> the generation of the equivalent message to stderr and an immediate
> return with non-zero return code. Note, the number of plexit calls is
> 220, from the results of
>
> find . -name "*.c" |xargs grep plexit | wc -l
>
> That number is roughly equivalent to the estimate I made above of the
> number of functions that would be affected by the propagation effort.
> That is the basis of my claim that the two efforts would be
> comparable.
There are also a few functions in the API that already return values
that would have to be changed. So this would also mean updating all of
the language bindings and probably some of the examples.
> 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.
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?
-Hazen
------------------------------------------------------------------------------
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
