On 09/14/2012 04:05 AM, Till Schneidereit wrote: > My question to the list is, then, what you all think I should work on > with the highest priority. > > Also, I'm not sure that updating the embedding API even makes sense > currently, what with the ongoing work on implementing a C++ API and > all.
If only. We're not working on a new C++ API, only adding little bits and pieces here and there that make sense as C++. We want a new C++ API that gets rid of all the non-standard bits and pieces and extensions in SpiderMonkey that involve so much extra work to support, a new API whose idioms straightforwardly map to spec idioms. A straightforward mapping would also mean these APIs would be much less likely to change in the future, because they wouldn't have bad modes of interaction with spec operations -- they'd *be* those operations to a large extent. But Gecko depends on those non-standard idioms too much right now to just remove them. We're working on removing them (see older .js-engine threads about removing some of the JSRESOLVE_* flags for examples of such work, and see the new DOM bindings for another huge chunk of work that'll help this), but I don't think we're at the point where we've cleaned out enough cruft yet to write or implement a truly good C++ API yet. For now, then, I think we do have to keep working on the embedding API docs, at least at keeping the per-method docs up-to-date. I worked on this a bit at the April doc sprint in San Francisco, mostly by looking at the dev-doc-needed bugs in the JS component and working on those bugs -- updating individual documentation pages, adding notes to release-note drafts, and so on. That's one thing that could certainly be done easily enough at a sprint, but it's possible there's higher-value stuff that could be worked on. I didn't give the matter much forethought before the sprint, so I just picked up the easiest thing to do that was close at hand. Jeff _______________________________________________ dev-tech-js-engine-internals mailing list dev-tech-js-engine-internals@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
