itaps-parallel Functions that need cloning for per-part queries

[Mark Shephard]

Just one comment that is general in nature and may or may not have any 
bearing to the decisions we need to make.

There is the assumption that having a small number of functions is the 
best answer. However, in an effort to make things as compact as 
possible, one can become vague in the functions. We (RPI SCOREC) have 
experience with software that actually goes the other direction where 
there is an insistence that the functions be very clear and because of 
that the number of functions is larger than if the focus was to keep the 
number at a minimum. Students here that have developed stuff have 
typically been more successful with the software that follows the second 
model. I guess my point is we should be focused on being sure our 
interfaces make sense and will be useful to those that we want to use 
it. Within that, let the number of functions be whatever comes out.

Mark

Carl Ollivier-Gooch wrote:
> Hello, all.
> 
> First, I apologize for being slower than I'd promised in getting these out.
> 
> Second, I apologize for an earlier miscount:  by the time we clone
> getNumOfType/Topo (twice each) and the global entity query functions and
> both sets of iterator functions (once each), there are a total of
> sixteen new functions, of which the whole-partition getNumOf* funcs are
> already mandated elsewhere.
> 
> Here they are; let the debate begin. :-)
> 
> Carl
>