Re: __{read,write}_once

To: Kamil Rytarowski <n54%gmx.com@localhost>
Subject: Re: __{read,write}_once
From: Robert Elz <kre%munnari.OZ.AU@localhost>
Date: Fri, 22 Nov 2019 08:42:19 +0700

    Date:        Fri, 22 Nov 2019 01:04:56 +0100
    From:        Kamil Rytarowski <n54%gmx.com@localhost>
    Message-ID:  <1a9d9b40-42fe-be08-d7b3-e6ecead5b55f%gmx.com@localhost>

  | I think that picking C11 terminology is the way forward.

Use a name like that iff the intent is to also exactly match the
semantics implied, otherwise it will only create more confusion.

kre

Follow-Ups:
- Re: __{read,write}_once
  - From: Kamil Rytarowski
- Re: __{read,write}_once
  - From: Martin Husemann

References:
- Re: __{read,write}_once
  - From: Kamil Rytarowski
- Re: __{read,write}_once
  - From: Maxime Villard
- Re: __{read,write}_once
  - From: Maxime Villard
- Re: __{read,write}_once
  - From: Mindaugas Rasiukevicius
- Re: __{read,write}_once
  - From: Maxime Villard
- Re: __{read,write}_once
  - From: Mindaugas Rasiukevicius
- Re: __{read,write}_once
  - From: Maxime Villard
- Re: __{read,write}_once
  - From: Mindaugas Rasiukevicius
- Re: __{read,write}_once
  - From: Maxime Villard
- Re: __{read,write}_once
  - From: Mindaugas Rasiukevicius
- Re: __{read,write}_once
  - From: David Holland
- Re: __{read,write}_once
  - From: Mindaugas Rasiukevicius
- Re: __{read,write}_once
  - From: David Holland
- Re: __{read,write}_once
  - From: Robert Elz

Prev by Date: PT32_[GS]ETXMMREGS for amd64 (Was: netbsd32_{,u}int64 in sys/types.h for compat/sys/siginfo.h)
Next by Date: Re: netbsd32_{,u}int64 in sys/types.h for compat/sys/siginfo.h
Previous by Thread: Re: __{read,write}_once
Next by Thread: Re: __{read,write}_once
Indexes:

Home | Main Index | Thread Index | Old Index