> > Théo Cavignac <[email protected]> writes: > > > Erratum: I think it did fix the bug, I just misunderstood a different > > error. Is this modification of coops config viable for upstream or should I > > find a way to grant thread safety in my own code ? > > > > Great! > > I see Felix is going to add the -disable-interrupts flag to the coops > egg. > > However, you may still need to compile your code that defines > coops thigs with -disable-interrupts. There are some macros in coops > that define complex functions. Those may still be non-thread safe.
The macros are all defining forms or used internally (mostly the sinister "build-cache"), so I don't see a need for that. But, will all things multithreaded, you can of course never be sure... felix _______________________________________________ Chicken-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-users
