W3C home > Mailing lists > Public > www-svg@w3.org > August 2000

SVGLists of type DOMString

From: Steve Dickson <sdickson@savagesoftware.com>
Date: Wed, 02 Aug 2000 15:13:57 -0700
Message-id: <fc.0085846d0000cf940085846d0000cf94.cf9f@savagesoftware.com>
To: www-svg@w3.org
Per the newly released Candidate Recommendation of Auguest 2, 2000. 
Section 4.3, Basic DOM interfaces, describes interface SVGTests.  This
interface includes an attribute requiredFeatures which is described as

"SVGList requiredFeatures
Corresponds to attribute requiredFeatures on the given element. The
various methods from SVGList, which are defined to accept
parameters and return values of type Object, must receive parameters of
type DOMString and return values of type DOMString."

This implicitly requires DOMString to inherit from Object.  In a Java
implementation, this would not be a problem, since all classes
automatically inherit from Object.  However, C++ doesn't have an inherent
Object class.  C++ implementations must create their own class Object, and
all classes which can be list members then derive from the Object class. 
By stipulating that DOMString can now be inserted into a list, DOMString
must derive from type Object.  This requires a change to the DOM.   

I think it's a bad idea to introduce features into SVGDOM that require
implementers to change/break the DOM.

This problem could be overcome by introducing a new interface SVGString
which derives from DOMString, and then have SVGTests use SVGString instead
of DOMString.   Any chance of this change making it into the next release?

Received on Wednesday, 2 August 2000 18:14:03 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:46:49 UTC