From: "Hollerer Franz, Schrack Seconet AG, Entwicklung" <f.hollerer@schrack-seconet.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"Ullrich Lucas, Schrack Seconet AG,
Entwicklung" <l.ullrich@schrack-seconet.com>
Subject: RE: [libgpiod]: feature request: API functions, const correctness
Date: Mon, 14 Aug 2023 08:16:03 +0000 [thread overview]
Message-ID: <5e106aba54904302bef2bc743ea6959b@schrack-seconet.com> (raw)
In-Reply-To: <CAMRc=Mcc7M3wbGX+77pUkQFTiPtDx3vYkWp=8eJWMh6k4eqhhw@mail.gmail.com>
Hi Bartosz!
I hesitate to follow your reasoning. I personally highly appreciate const correctness as it IMHO makes the intend of the code clearer, prevents misuse, and gives the compiler more options for warnings and optimization.
Anyway, it's your choice and I respect this.
Franz
next prev parent reply other threads:[~2023-08-14 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 14:06 [libgpiod]: feature request: API functions, const correctness Hollerer Franz, Schrack Seconet AG, Entwicklung
2023-08-12 18:42 ` Bartosz Golaszewski
2023-08-14 8:16 ` Hollerer Franz, Schrack Seconet AG, Entwicklung [this message]
2023-08-14 9:56 ` Bartosz Golaszewski
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=5e106aba54904302bef2bc743ea6959b@schrack-seconet.com \
--to=f.hollerer@schrack-seconet.com \
--cc=brgl@bgdev.pl \
--cc=l.ullrich@schrack-seconet.com \
--cc=linux-gpio@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox