[bug #28900] GDL2 fails to build due to GSLazyRecursiveLock

[David Ayers]

Update of bug #28900 (project gnustep):

                  Status:                    None => In Progress            
             Assigned to:                    None => ayers                  

    _______________________________________________________

Follow-up Comment #2:

Sorry for the delay.  I haven't been following bugreports as closely as I
should have.  Feel free to assign GDL2 issues to me.

I have no issue with removing the macro.  The newLockAt: is convenience
extension to avoid a race for plugins that get loaded into an already
multithreaded environment.

If there is some canonical approach on how to deal with such situations, I'll
be happy to use it.  Until then I'll implement an approach that relies on the
runtime's +initialize semantics and will be GDL2 internal.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?28900>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/