[MTASCsft PATCH 01/??] MT-, AS- and AC-Safety docs

[Alexandre Oliva]

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

> Just like signal handlers, cancellation cleanup routines must
> configure the floating point environment they require. The routines 
> cannot assume a floating point environment, particularly when
> asynchronous cancellation is enabled.  If the configuration of a 
> the floating point environment cannot be performed atomically then it
> is also possible that the environment encountered is internally
> inconsistent.

I put this in, with s/a\nthe/the/.

> IMO the discussion two FPU systems is beyond the scope of this text.

>> +the accesses are well defined.  The notion that users are expected to
>> +safeguard against data races any objects of their choice that the
>> +library accesses on their behalf prevails.

> This last sentence remains awkward.

> Suggest rewording as follows:

> The notion prevails that users are expected to safeguard against data
> races any objects that the library accesses on their behalf.

I like that, except for dropping the “of their choice”; that would turn
all cases of @mtasurace into @mtsrace.

I'm taking that with s/objects/user-supplied objects/, if you don't
mind.

Ok to install with these two changes?


-- 
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