Re: [heycam/webidl] Fix internal methods that only target platform objects w/ indexed/named props (#202)

I think I gave some bad advice here. I thought that the current setup was contradictory, since the intro paragraphs say "this only applies for objects that support named/indexed props", but then there are fallback steps outside of those for named/indexed props. But of course now I realize those steps are for the rest of the properties of the object (the non-named/indexed ones). So the current spec is not broken, like I thought it was and told @tobie it was.

I would still prefer a clearer setup, however, where there are _n_ types of exotic objects, and they all have internal method definitions that apply in every case, not just sometimes. A simple way to do this is to have n = 1, with the only type of exotic object being "platform object", and then we just define all the internal methods, with some if statements inside them. I guess you could go for n = 2 (platform objects and named-or-indexed platform objects), or even n = 4 (those two multiplied by legacy-caller-or-not).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/202#issuecomment-255847868