linux-kernel - Re: [PATCH 5/7] kconfig: qconf: use nullptr in C++11 code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAK7LNARSM=EDgHN9=j1-BXoeZ5aq8O+nCZeBUeGrvhq2+1fQvQ@mail.gmail.com>
Date: Thu, 24 Oct 2024 01:41:09 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: Rolf Eike Beer <eb@...ix.com>
Cc: linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/7] kconfig: qconf: use nullptr in C++11 code

On Wed, Oct 23, 2024 at 3:35 PM Rolf Eike Beer <eb@...ix.com> wrote:
>
> This is type safe as it can't be accidentially assigned to something not a
> pointer.

This is incomplete because there are more call sites that use
0 instead of nullptr.

For example, you can replace nextItem(0) with nextItem(nullptr)

Anyway, I do not need this patch for now because qconf is
under refactoring, and I will remove a lot of code.

Please come back with a more comprehensive patch
some months later if you are still interested.

--
Best Regards
Masahiro Yamada