Re: [heycam/webidl] Add namespaces (#121)

> +                <a>!</a> <a>ObjectCreate</a>(the <a>%ObjectPrototype%</a> of <var>realm</var>).
> +              </li>
> +
> +              <li>
> +                For each <a class='dfnref' href='#dfn-exposed'>exposed</a> <a class='dfnref'
> +                href='#dfn-regular-operation'>regular operation</a> <var>op</var> that is a <a
> +                class='dfnref' href='#dfn-namespace-member'>namespace member</a> of this namespace,
> +
> +                <ol>
> +                  <li>
> +                    Let <var>id</var> be <var>op</var>'s <a class='dfnref'
> +                    href='#dfn-identifier'>identifier</a>.
> +                  </li>
> +
> +                  <li>
> +                    Let <var>steps</var> be the following series of steps, given function argument

This was somewhat of an attempt to modernize that section to do things like state that methods are built-in functions (#106) and give property descriptors for name and length, and state the realm of the function. It also moves us toward a world where instead of stating what operations MUST be, we give an explicit procedure for creating interface objects and namespace objects. As I said in the OP, "The ES binding for namespaces here is written in a fully modern style, and so differs slightly from similar prose for interfaces' ES binding. It is hoped that it can provide a template for eventually updating interfaces' ES binding to modern ES."

Let me try factoring out this modern way of creating operations and replacing much of the existing #es-operations section with it. Then we can call into it from namespaces, and in the future call into it from interface objects.

-- 
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/pull/121/files/23ba5276699574269bd955c67d60bd6ce586337f#r76300751