The open source OpenXR runtime
doc: Update conventions with function typedefs
+4
-1
+4
-1
doc/conventions.md
+4
-1
doc/conventions.md
···
50
50
*implemented* in other modules.)
51
51
- Generally, we do not declare typedefs for `struct` and `enum` types, but
52
52
instead refer to them in long form, saying `struct` or `enum` then the name.
53
-
- If a typedef is needed, it should be named ending with `_t`.
53
+
The exception to not using typedefs is function pointers used as function
54
+
arguments as these become very hard to both read and type out.
55
+
- If a typedef is needed, it should be named ending with `_t`. Function
56
+
pointer typedefs should end with `_func_t`.
54
57
- Parameters: `lower_snake_case` or acronyms.
55
58
- Output parameters should begin with `out_`.
56
59
- Of special note: Structures/types that represent "objects" often have long