mfbt/STYLE
author Nathan Froyd <froydnj@mozilla.com>
Thu, 28 Jun 2018 09:04:41 -0400
changeset 479410 58e5f6f08c54a318e59cd5ef1482602e3a68ddf0
parent 378420 89b895c219f2b97fc0ded8877b30c337e697bdaa
permissions -rw-r--r--
Bug 1451104 - part 1 - ensure compatible binutils for GCC; r=glandium GCC will pick up whatever `as` is first in PATH when trying to assemble files. It expects this `as` to have at least as many features as the `as` detected at configure time when GCC was originally built. We should ensure that GCC is always picking up an appropriate `as` by adding its base directory to the search path; otherwise, we get peculiar assembler errors.

MFBT uses standard Mozilla style, with the following exceptions.

- Some of the files use a lower-case letter at the start of function names.
  This is because MFBT used to use a different style, and was later converted
  to standard Mozilla style. These functions have not been changed to use an
  upper-case letter because it would cause a lot of churn in other parts of the
  codebase. However, new files should follow standard Mozilla style and use an
  upper-case letter at the start of function names.

- Imported third-party code (such as decimal/*, double-conversion/source/*, and
  lz4*) remains in its original style.