Re: scm_i_fraction_reduce thread safety

[Marius Vollmer]

Kevin Ryde <address@hidden> writes:

> Marius Vollmer <address@hidden> writes:
>>
>> User code should only use scm_numerator and scm_denominator to access
>> parts of the fraction object and those functions will first reduce the
>> fraction (in a thread safe way).  Wouldn't that be enough?
>
> Yep, though it seems a shame the accessors have to be slowed down just
> so printing and equality can write back.

Is that slow down significant?  The logic could be like

  if fraction is not reduced:
    lock
    if fraction is not reduced:
      reduce it
    unlock
  read it

So in the common case of a reduced fraction, no locks would be
necessary.  (This works since a fraction can never go from reduced to
unreduced.)

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405