Here it is, in all its greatly untested glory: http://pastebin.ca/109242
I don't know how much error it has, but the error won't stack up: if
it's one second off, it will remain one second off until the end of
time, or until your system clock drifts. But system clock drifts will
be fixed by synch
Frederik Eaton wrote:
On Mon, Jul 31, 2006 at 03:09:59PM +0300, Einar Karttunen wrote:
On 31.07 03:18, Frederik Eaton wrote:
4) the library runs the callback code in Tw where the TLS state is
invalid. This is even worse than a global variable in this case.
If you have threads, and you have
Dear all,
The Scheme and Functional Programming Workshop
pre-registration deadline is in about 2 and a half weeks --
do be sure to register for ICFP and the workshop before
then.
Come to hear Manuel Serrano talk about HOP, his new language
for programming the web, a status report from the R6RS
ed
On Mon, Jul 31, 2006 at 03:09:59PM +0300, Einar Karttunen wrote:
> On 31.07 03:18, Frederik Eaton wrote:
> > I don't think it's necessarily such a big deal. Presumably the library
> > with the worker threads will have to be invoked somewhere. One should
> > just make sure that it is invoked in the
On 31.07 14:03, Thomas Conway wrote:
> This is why I believe transaction-local variables are a more useful concept.
> You are garanteed that there is only one thread accessing them, and
> they behave just like ordinary TVars except that each transaction has
> its own copy.
This seems like it could
On 31.07 03:18, Frederik Eaton wrote:
> I don't think it's necessarily such a big deal. Presumably the library
> with the worker threads will have to be invoked somewhere. One should
> just make sure that it is invoked in the appropriate environment, for
> instance with the database connection alre
Dear Haskellers,
The following paper may still benefit from your comment.
The final version is only due per 10 August 2006.
Thanks,
Ralf Laemmel
--
http://homepages.cwi.nl/~ralf/gpce06/
Title: Software Extension and Integ
