[MTASCsft PATCH 28/??] MT-, AS- and AC-Safety docs: manual/socket.texi

[Alexandre Oliva]

On Jan 31, 2014, "Carlos O'Donell" <carlos@redhat.com> wrote:

> On 01/27/2014 10:13 PM, Alexandre Oliva wrote:
>> In this file I introduce the pattern of documenting <dataset>ent
>> functions that hold internal iteration state with @mtasurace{:<dataset>}
>> and, in addition to it, for those that use a static buffer to hold the
>> return value, @mtasurace{:<dataset>buf}.
 
> But a user has no idea what the `:identifier' means, it's only an
> opaque marker for similar functions with similar problems. The user
> can't infer anything from so marked functions other than they share
> the same problem so avoiding all of them avoids that particular
> problem. Right?

Yeah.  And if she wants to call them anyway, it suffices to take the
measures specified under “race”, namely holding a separate mutex for
each named identifier, to be able to call them MT-Safely (but not
AS-Safely, for this approach may deadlock).

-- 
Alexandre Oliva, freedom fighter    http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/   FSF Latin America board member
Free Software Evangelist     Red Hat Brazil Toolchain Engineer