iRel revisions

[Mark Shephard]

Was suppose to be;

Note that ....

(lost and e)

Mark Shephard wrote:
> Tim,
> 
> Not that RPI and Simmetrix are pretty much unable to make any progress 
> until the iterator-based functions. We need them as soon as possible.
> 
> Mark
> 
> Tim Tautges wrote:
>>
>>
>> Carl Ollivier-Gooch wrote:
>>> Tim Tautges wrote:
>>>> Hi all,
>>>>   Based on our discussions about iRel, I've made changes to the iRel 
>>>> interface header; the new version is attached, along with a revised 
>>>> document describing iRel.  Comments are welcome.  When things have 
>>>> settled down from that, I'll get this in to the ITAPS repo and 
>>>> implement the changes in Lasso.
>>>
>>> A couple of comments, mostly minor:
>>>
>>> There are a couple of paste-o's where the arg type in 
>>> iBase_EntitySet, but the arg name is ent*.
>>>
>>
>> Got it.
>>
>>> There's a comment at the top of the file that suggests that some 
>>> functions will take either an entity or a set in the same argument 
>>> slot, with an additional arg indicating which it is.  That doesn't 
>>> show up anywhere in the file (which is good, because compilers would 
>>> puke on that), but the comment should be removed.
>>
>> Oops;  I thought I'd expunged all MOAB-based assumptions from iRel, 
>> but they persist, as does Carl's vigilance :).
>>
>>>
>>> Otherwise --- and with the caveat that I've not tried to implement or 
>>> use it --- this looks reasonable enough to me as far as it goes.  
>>> Isn't it still missing some stuff about returning iterators instead 
>>> of sets on request?
>>>
>>
>> Drat, I guess my subconscious was trying to slip that one past the 
>> group.  Mark B, this was (on a conscious level, anyway...) unintentional.
>>
>> Looks like there's more work to do to add iterator-based functions.  I 
>> may not get to this until next week, but I'll get to it.
>>
>>> Carl
>>>
>>>
>>>
>>
>> A couple other changes:
>>
>> - removed setSetArrEntArr, that's covered by setEntArrSetArr with 
>> appropriate switch_order argument.  For those that are really on top 
>> of things (Carl), I think the setSetEntArr has to stay, because of 
>> non-symmetry in the Arr part.
>>
>> - removed comment block on Geometry-Mesh Functions, which were removed 
>> from iRel
>>
>> - tim
>>
>