On 12/25/2013, 4:46 PM, Mike Hommey wrote:
On Wed, Dec 25, 2013 at 10:00:33PM +1300, Robert O'Callahan wrote:
The JS engine has always been a problem when trying to enforce consistent
standards across Gecko. Part of that comes from it being viewed as an
independent product, much more so than any other Gecko module. Another part
of that is due to the JS engine having particularly, um, "strong" module
owners :-).
Therefore JS has always had its own style. Since MFBT is a base for both JS
and the rest of Gecko, this put MFBT in a difficult position. Creating a
third style probably wasn't a good choice, though.
The sad part is JS used to be C. Its idiosyncratic C++ rules could have
been inherited from Gecko instead.
FWIW this is the earliest version of the SpiderMonkey coding style
document that I can find, dating back to 2006:
<https://wiki.mozilla.org/index.php?title=JavaScript:SpiderMonkey:C_Coding_Style&oldid=15815>.
That document only lists a number of JS specific conventions, which is
fine. At some point that changed and the document started to diverge
from the Mozilla coding style. I don't recall a discussion on the
rationale but perhaps my memory is not serving me.
Cheers,
Ehsan
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
