W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2005

[whatwg] ECMAScript extensions in Web Applications

From: Ian Hickson <ian@hixie.ch>
Date: Sun, 16 Oct 2005 00:53:49 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0510160026500.23945@dhalsim.dreamhost.com>
On Sat, 15 Oct 2005, Krzysztof Maczynski wrote:
>
>> From http://www.whatwg.org/specs/web-apps/current-work/:
> 
> "In the ECMAScript binding itself, however, the handleEvent() method of 
> the interface is not directly accessible on Function objects. Such 
> functions must be called in the global scope."
> 
> Why is that? Only to declare current browsers compliant?

Yes.


> Reflection mechanisms (abound in ECMAScript) will be of limited use, 
> especially in multi-language programming. Special treatments will need 
> to be hardwired into development tools (debuggers, inspectors, wizards, 
> code editing assistants, metadata handlers). Disobeying design 
> principles sooner or later tends to turn out to be short-sightedness.
>
> If you really want at this price to legitimate current implementations, 
> at least make this hideous practice optional, not mandatory. And 
> deprecated from the start.

I'm not really sure what you're proposing. Are you suggesting that any 
Function object should have a .handleEvent() method in addition to its 
.call() method and its .prototype attribute? What would be the point?

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Saturday, 15 October 2005 17:53:49 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:43 UTC