Re: __{read,write}_once

To: Maxime Villard <max%m00nbsd.net@localhost>
Subject: Re: __{read,write}_once
From: Andreas Gustafsson <gson%gson.org@localhost>
Date: Fri, 22 Nov 2019 11:29:25 +0200

Maxime Villard wrote:
> How about _onestep()? Or _nosplit()?

Or just conclude that there are no good options and we might as well
call it _once() to be compatible with other OSes.
-- 
Andreas Gustafsson, gson%gson.org@localhost

References:
- 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: Maxime Villard
- Re: __{read,write}_once
  - From: David Young
- Re: __{read,write}_once
  - From: Maxime Villard

Prev by Date: Re: __{read,write}_once
Next by Date: Re: PT32_[GS]ETXMMREGS for amd64 (Was: 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