I'll take a look, but it's worth noting that the thread-safety of lazy is not at issue here: sks is a single-threaded program. And if someone wanted to make it multi-threaded, I would propose using a cooperative threading library like async or lwt, which would preserve the safety of Lazy.
y On Sat, May 5, 2012 at 10:57 PM, Jens Leinenbach <j...@ccc-hanau.de> wrote: > Hi John, > > I attached my changes as a patch. It should not break an existing SKS > installation and it should be easy to compile it for Debian with just a > few easy changes in settings.ml and adding the needed paths to sksconf. > (Changes for the example sksconf for Debian included.) > > Then I removed all those "lazy" instructions. I have no idea why they > were used and they just caused trouble here and it works great without > them. > > Additionally, "Lazy.force" was uses several times, but it is not > thread-safe: > http://caml.inria.fr/pub/docs/manual-ocaml/libref/Lazy.html > > Please let me know what you think about my changes. > > > Cheers > Jens > > > _______________________________________________ > Sks-devel mailing list > Sks-devel@nongnu.org > https://lists.nongnu.org/mailman/listinfo/sks-devel > >
_______________________________________________ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
