Khronos Public Bugzilla
Bug 84 - newparam different in Profile_gles2 to other profiles
newparam different in Profile_gles2 to other profiles
Status: ASSIGNED
Product: COLLADA
Classification: Unclassified
Component: Schema
1.5.0
PC Windows
: P3 minor
: ---
Assigned To: Fabrice Robinet
COLLADA Work Group email alias
: collada-fx
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-08-15 14:06 PDT by Dan Bartlett
Modified: 2014-01-07 10:23 PST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Bartlett 2008-08-15 14:06:38 PDT
In Profile_GLES2, newparam is defined as:

<xs:element name="newparam" minOccurs="0" maxOccurs="unbounded">
  <xs:complexType>
    <xs:complexContent>
      <xs:extension base="gles2_newparam_type"/>
    </xs:complexContent>
  </xs:complexType>
</xs:element>

but in other profiles, defined as such:

<xs:element name="newparam" type="glsl_newparam_type" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="newparam" type="gles_newparam_type" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="newparam" type="cg_newparam_type" minOccurs="0" maxOccurs="unbounded"/>

This can result in different code with auto-generated code.
Comment 1 Mark Barnes 2008-08-29 12:09:40 PDT
It looks like there is no reason for the GLES2 profile to be different. It's not really extending the type in the final schema (although it may been in some earlier draft). Thanks for spotting this cruft Dan.