On Wednesday, May 12, 2010, at 04:01PM, "Tom Browder" <tom.brow...@gmail.com>
wrote:
>Right now I read the attributes and take them as I find them (and
>report unknown attributes found), but I sure like the idea of better
>BRL-CAD attribute standards. How would you implement the case
>insensitivity?
It would be implemented by the low-level attribute routines in librt and libbu.
Particularly for the lookup routines in librt, like db_lookup_by_attribute(),
it would merely compare the keys case insensitively. Almost all of the
attribute routines go through libbu so the biggest change would be to routines
like bu_avs_add() where it would be changed to compare names case-insensitively
(and then store the name it was comparing against in order to be
case-preserving).
To make it work well, we should provide routines in librt that do exactly what
you mentioned for identifying unknown and/or non-standard attributes.
>> air flag ('air')
>
>I like "air_code" better, but I'm not going to the mat over it.
Is it a code or a flag? To me, code implies that there are a set of valid
values similar to material identifiers that map to something. If it's a flag
(on/off) to mark something as representing 'air' similar to how 'region' is a
flag for denoting regions, then we should be consistent.
Cheers!
Sean
------------------------------------------------------------------------------
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
