mirror of
https://gitlab.freedesktop.org/wayland/wayland-protocols.git
synced 2025-12-25 01:20:09 +01:00
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>
This commit is contained in:
parent
0c7973d72b
commit
a3023a86ab
1 changed files with 15 additions and 0 deletions
15
README
15
README
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue