Deutsch English Français Italiano |
<v6bavg$3pu5i$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Thiago Adams <thiago.adams@gmail.com> Newsgroups: comp.lang.c Subject: question about nullptr Date: Sat, 6 Jul 2024 08:49:04 -0300 Organization: A noiseless patient Spider Lines: 13 Message-ID: <v6bavg$3pu5i$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Sat, 06 Jul 2024 13:49:05 +0200 (CEST) Injection-Info: dont-email.me; posting-host="095a8db42943cdf13a48c4cf816b5ad7"; logging-data="3995826"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+3/XoAdmHo/rcr1v8i/kUS0D8orbF3XMI=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:gmGhjdjxJu4mcrz2ON6PKjgqvOA= Content-Language: en-GB Bytes: 1442 If you were creating C code today and could use a C23 compiler, would you use nullptr instead of NULL? I am asking because I think I will keep using NULL. I like nullptr semantics but I don't like to introduce new element (nullptr) inside the code with no guarantee that the code will not mix both. In the past we also didn't have a guarantee we are not mixing 0 or NULL. I think the best scenario for a team guideline would be a style warning if 0 or nullptr is used and NULL to be defined as nullptr in a C23 compiler.