diff options
author | Jonas Ådahl <jadahl@gmail.com> | 2015-11-06 12:33:01 +0800 |
---|---|---|
committer | Jonas Ådahl <jadahl@gmail.com> | 2015-11-09 15:04:24 +0800 |
commit | a3023a86ab42b0e6fb89a1e0856a73fa5f753ae1 (patch) | |
tree | dba63a1583ccb29d8ede1b1533009d532b6878ad | |
parent | 0c7973d72bf5e96442203d4d70c95c388dd1d194 (diff) |
README: Document interface naming convention
Document that what different types of protocols should prefix their
interfaces with.
Signed-off-by: Jonas Ådahl <jadahl@gmail.com>
-rw-r--r-- | README | 15 |
1 files changed, 15 insertions, 0 deletions
@@ -51,6 +51,21 @@ describe above. If the changes are backward incompatible changes to an unstable protocol, see <<Unstable protocol changes>>. +Interface naming convention +~~~~~~~~~~~~~~~~~~~~~~~~~~~ +All protocols should avoid using generic namespaces or no namespaces in +the protocol interface names in order to minimize risk that the generated +C API collides with other C API. Interface names that may collide with +interface names from other protocols should also be avoided. + +For generic protocols not limited to certain configurations (such as +specific desktop environment or operating system) the +wp_+ prefix +should be used on all interfaces in the protocol. + +For operating system specific protocols, the interfaces should be +prefixed with both +wp_+ and the operating system, for example ++wp_linux_+, or +wp_freebsd_+, etc. + Unstable naming convention ~~~~~~~~~~~~~~~~~~~~~~~~~~ Unstable protocols have a special naming convention in order to make it |