Open Bug 1677280 Opened 5 years ago Updated 4 years ago

Have a naming convention for header fragments

Categories

(Developer Infrastructure :: Source Code Analysis, task, P5)

Product:
Developer Infrastructure
Component:
Source Code Analysis
Type:
task

Tracking

(Not tracked)

People

(Reporter: sg, Unassigned)

References

Details

There are several header fragment files that cannot be included in arbitrary contexts and don't have header guards, such as the StaticPrefList_*.h files. These should not be named "*.h"to make their status clear, and avoid them being mistaken as candidates for inclusion.

*.inc?

Bike-shedding time!😄

I think it'd be great if it was a unique file extension, so that our favorite IDEs can be trained to parse these as C++.
.inc is already used a lot, and not only for C/C++.
.hpp and .hh are used a lot.
.hxx is only used in one directory: extensions/spellcheck/hunspell/src, so that could be a candidate.
Or make it more obvious, e.g.: .cinc and .cppinc (not used yet).

Priority: -- → P5
Product: Firefox Build System → Developer Infrastructure
You need to log in before you can comment on or make changes to this bug.