proposals for enumeration of interface-specific error codes

[Jason Kraftcheck]

On 08/24/2010 12:15 PM, Miller, Mark C. wrote:
>>
>> kraftche at cae.wisc.edu wrote:
 >>
>>
>> The specific requirement was to support implementations that do
>> getDescription by indexing into an array.
>
> Unless we are talking about error codes whose 'value's number in the tens of
 > thousands, then I don't see why a sparse array is a problem here.
>

But if one works around the sparsness correctly, then the other issues 
go away as well and the implementation is probably more robust.  But the 
whole point of this was that some did not want to implement things that way.

>
>> Further, the cosmetic factors are significant in this case.  It would be
>> unnecessarily difficult and error prone for a user of the interface to
>> determine what subset of the error codes they expect to need to deal
>> with if they are an interleaved mess.
>
> Oh, come on. grep iMesh_ iBase.h will give me the list just fine.
>

Perphaps.  But why require (even trivial) processing when it is also 
trivial to group them in the header, making the whole thing more 
self-documented.

- jason