From: Patrick Williams <patrick@stwcx.xyz>
To: Adriana Kobylak <anoo@linux.ibm.com>
Cc: OpenBMC List <openbmc@lists.ozlabs.org>,
openbmc <openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org>
Subject: Re: sdbusplus - const/readonly flags
Date: Wed, 26 Aug 2020 10:10:19 -0500 [thread overview]
Message-ID: <20200826151019.GM3532@heinlein> (raw)
In-Reply-To: <421fddd2a3f5b352f0cd5b260216bc8b@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
On Tue, Aug 25, 2020 at 03:52:42PM -0500, Adriana Kobylak wrote:
> On 2020-08-25 10:00, Patrick Williams wrote:
>
> > * I expect some of the 'const' flags in phosphor-dbus-interfaces are
> > wrong and should be changed to 'readonly'. I have collected a
> > list
> > of them in a gist[4]. If you really intend to mean "this property
> > will never change during the life of an object" continue to use
> > 'const', but if you mean "this property shall not be changed by
> > clients", use 'readonly' (and probably also add 'emits_change').
>
> There are also some properties in phosphor-dbus-interfaces with
> descriptions that say "read-only property", and the implementation is
> enforcing it. It may good for the owners to revisit those as well and
> see if a 'read-only' flag is applicable.
Yes, that's also a good point. If there are any descriptions that say
read-only property we should transition those to using the read-only
flag so it is enforced automatically at a code level.
Here is another gist with all the variations I found of "read-only".
https://gist.github.com/williamspatrick/03d72260982332c786770d0678644f94
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-08-26 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 15:00 sdbusplus - const/readonly flags Patrick Williams
2020-08-25 17:50 ` Matthew Barth
2020-08-25 18:08 ` Patrick Williams
2020-08-25 20:52 ` Adriana Kobylak
2020-08-26 15:10 ` Patrick Williams [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200826151019.GM3532@heinlein \
--to=patrick@stwcx.xyz \
--cc=anoo@linux.ibm.com \
--cc=openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.