- From: Boris Zbarsky <notifications@github.com>
- Date: Fri, 13 May 2016 07:14:11 -0700
- To: heycam/webidl <webidl@noreply.github.com>
- Cc:
- Message-ID: <heycam/webidl/pull/121/r63189274@github.com>
> + > +partial namespace <em>SomeNamespace</em> { > + <i>namespace-members…</i> > +};</pre> > + > + <div class='note'> > + <p> > + As with partial interface definitions, partial namespace definitions are intended for > + use as a specification editorial aide, allowing the definition of an interface to be > + separated over more than one section of the document, and sometimes multiple > + documents. > + </p> > + </div> > + > + <p> > + The order that members appear in has no significance except in the case of <a I know you copied this from the text for interfaces, but is this actually true? I don't see how order matters in the case of overloading, but in the _non-overloading_ case it does matter in practice, though not per spec: it affects the order in which the properties appear in `Object.getOwnPropertyNames(namespaceObj)`. Per spec the order of properties is not defined, I guess. --- 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/70ba6d9c213e2b05cf0d8b3ebd14ce9a4583f4c6#r63189274
Received on Friday, 13 May 2016 14:14:38 UTC