Attachment 46823 Details for Bug 37095 – [PATCH 4/9] Describe conventional naming of methods and signals

[patch] [PATCH 4/9] Describe conventional naming of methods and signals

0004-Describe-conventional-naming-of-methods-and-signals.patch (text/plain), 1.11 KB, created by Simon McVittie on 2011-05-17 09:12:32 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Simon McVittie

Created: 2011-05-17 09:12:32 UTC

Size: 1.11 KB

patch

obsolete

>From 977c7a7c4a01ba3fad919d20404865144417d9f6 Mon Sep 17 00:00:00 2001
>From: Simon McVittie <simon.mcvittie@collabora.co.uk>
>Date: Tue, 17 May 2011 17:06:21 +0100
>Subject: [PATCH 4/9] Describe conventional naming of methods and signals
>
>---
> doc/dbus-specification.xml |    8 ++++++++
> 1 files changed, 8 insertions(+), 0 deletions(-)
>
>diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml
>index 4045513..6d2b26a 100644
>--- a/doc/dbus-specification.xml
>+++ b/doc/dbus-specification.xml
>@@ -1290,6 +1290,14 @@
> 	    <listitem><para>Must be at least 1 byte in length.</para></listitem>
>           </itemizedlist>
>         </para>
>+
>+        <para>
>+          It is conventional for member names on D-Bus to consist of
>+          capitalized words with no punctuation ("camel-case").
>+          Method names should usually be verbs, such as
>+          <literal>GetItems</literal>, and signal names should usually be
>+          a description of an event, such as <literal>ItemsChanged</literal>.
>+        </para>
>       </sect3>
>       <sect3 id="message-protocol-names-error">
>         <title>Error names</title>
>-- 
>1.7.5.1
>

Actions: View | Splinter Review

Attachments on bug 37095: 46820 | 46821 | 46822 | 46823 | 46824 | 46825 | 46826 | 46827 | 46828 | 126931

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.