Subtle bug fix: When we were selecting a single vec/color/matrix component, we botched the generation of the new type that described the component by correctly setting its aggregateness to SCALAR but forgetting to clear any vector semantics (should have set to NOXFORM but instead would leave it as COLORXFORM or POINTXFORM or whatever).  This was a mostly silent error, except that then this incorrectly-constructed scalar would not compare properly to a "real" scalar.
Subtle bug fix: When we were selecting a single vec/color/matrix
component, we botched the generation of the new type that described the
component by correctly setting its aggregateness to SCALAR but
forgetting to clear any vector semantics (should have set to NOXFORM but
instead would leave it as COLORXFORM or POINTXFORM or whatever).  This
was a mostly silent error, except that then this incorrectly-constructed
scalar would not compare properly to a "real" scalar.

qdtk/openshadinglanguage,tectronics/openshadinglanguage,code-google-com/openshadinglanguage,code-google-com/openshadinglanguage,qdtk/openshadinglanguage,h3rb/openshadinglanguage,h3rb/openshadinglanguage,tectronics/openshadinglanguage,code-google-com/openshadinglanguage,code-google-com/openshadinglanguage,tectronics/openshadinglanguage,qdtk/openshadinglanguage,h3rb/openshadinglanguage,tectronics/openshadinglanguage,h3rb/openshadinglanguage,qdtk/openshadinglanguage