Re: 'long' Object Type?

On Wed, 2003-09-24 at 11:13, Gavin Kistner wrote:
> Several properties in
> 	http://www.w3.org/TR/DOM-Level-2-Events/ecma-script-binding.html
> are referred to being a long object, as in:
> 
> 	screenX
> 		This read-only property is a long object.
> 
> I assume this is supposed to mean 'long integer', since neither DOM 2 
> Events or DOM 2 Core define this type of object. This is fine for the 
> public specification, but for this ECMAScript binding this should be 
> Number, should it not? (ECMAScript does not have a dedicated object 
> type for integers as opposed to floats.)
> 
> Or is there a 'long' object described somewhere that I'm missing?
> 
> (I ask because I'm pulling the specs into a DB:
> 	http://phrogz.dnsalias.net/ObjJob/
> to both encapsulate inheritance hierarchy and also allow browsing of 
> the full properties/methods available to an object through its 
> inheritance, and my parser sort or hiccupped on this 'long' object, e.g.
> 	http://phrogz.dnsalias.net/ObjJob/method.asp?id=612
> and I'd love to be able to change it to a number and assign it to the 
> ECMAScript Core language if that's the correct thing to do.)
> 
> I can't seem to subscribe to this mailing list, so please CC me on 
> replies.

This error has been fixed in DOM Level 3. The DOM WG did not go through
its errata TODO list for quite sometimes [1]

[1] On Wed, 2003-09-24 at 11:13, Gavin Kistner wrote:
> Several properties in
> 	http://www.w3.org/TR/DOM-Level-2-Events/ecma-script-binding.html
> are referred to being a long object, as in:
> 
> 	screenX
> 		This read-only property is a long object.
> 
> I assume this is supposed to mean 'long integer', since neither DOM 2 
> Events or DOM 2 Core define this type of object. This is fine for the 
> public specification, but for this ECMAScript binding this should be 
> Number, should it not? (ECMAScript does not have a dedicated object 
> type for integers as opposed to floats.)
> 
> Or is there a 'long' object described somewhere that I'm missing?
> 
> (I ask because I'm pulling the specs into a DB:
> 	http://phrogz.dnsalias.net/ObjJob/
> to both encapsulate inheritance hierarchy and also allow browsing of 
> the full properties/methods available to an object through its 
> inheritance, and my parser sort or hiccupped on this 'long' object, e.g.
> 	http://phrogz.dnsalias.net/ObjJob/method.asp?id=612
> and I'd love to be able to change it to a number and assign it to the 
> ECMAScript Core language if that's the correct thing to do.)
> 
> I can't seem to subscribe to this mailing list, so please CC me on 
> replies.

This error has been fixed in DOM Level 3. The DOM WG did not go through
its errata TODO list for quite sometimes, and we really should.

Philippe

[1] http://lists.w3.org/Archives/Public/www-dom/2003JulSep/0018.html

Received on Thursday, 23 October 2003 12:33:15 UTC