Doxygen output?

2017-02-19 Thread Henri Sivonen
Our comments mostly try to follow the Doxygen format, and MDN says that the documentation team has a tool for importing Doxygen-formatted IDL comments into MDN articles. Other than that, is Doxygen output from m-c input being published anywhere? https://people-mozilla.org/~bgirard/doxygen/gfx/ is

Re: Mozilla naming style vs. C++ standard library containers

2017-02-19 Thread Henri Sivonen
On Thu, Feb 16, 2017 at 9:09 PM, Botond Ballo wrote: > In the case of begin() and end(), it's not just a matter of style. It seems that nsTArray, too, mixes these into a class that otherwise follows Mozilla naming, so I guess we have enough precedent for using the standard-library naming for iter

Re: Should &&/|| really be at the end of lines?

2017-02-19 Thread Martin Thomson
On Mon, Feb 20, 2017 at 3:18 AM, smaug wrote: > I don't care too much about &&/|| coding style, though the current style > does feel easier to > read, per the reasoning dmajor gave. I suspect that a lot of people think this way. While it's tempting to suggest that arguments like "that's the way

New sync IPC messages will require IPC peers' review

2017-02-19 Thread Kan-Ru Chen
Hi, In order to reduce the performance issues caused by sync IPC messages, we are tracking and removing sync IPCs from the content process or the UI thread[1]. With bug 1336919 landed[[2] all additions of new sync messages must be recorded in ipc/ipdl/sync-messages.ini and reviewed by an IPC peer.

Re: Should &&/|| really be at the end of lines?

2017-02-19 Thread smaug
On 02/18/2017 07:08 PM, Eric Rescorla wrote: I'd also note that if we're not going to use "this is what we have done historically" as a guide, then it seems like much bigger changes are on the table and we would probably be better off adopting some other well-defined coding standard wholesale (e