Re: [Chicken-users] new egg: simple-timer
Hi Jörg, On 25 Nov 2018 18:21:29 +0100 Jörg F. Wittenberger wrote: > Thanks Mario, > > I tagged a better version. Thanks. I've added your egg to the coop. All the best. Mario -- http://parenteses.org/mario ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] new egg: simple-timer
Thanks Mario, I tagged a better version. Best /Jörg On Nov 24 2018, Mario Domenech Goulart wrote: Hi Jörg, On 24 Nov 2018 21:59:08 +0100 Jörg F. Wittenberger wrote: I packages a new new: simple-timer https://raw.githubusercontent.com/0-8-15/simple-timer/master/simple-timer.release-info This is intended as the one-stop shopping for low level plumping of the background threads every other egg needs to put at the core's timeout queue. (Either because it needs roughly correct time signals or evade false deadlock detection.) I hope this could help with is the hell of reasoning about the timeout queue in an application using several such eggs at the same time: At least the boring timeouts are under a single umbrella. Right now it is just the code the `forcible` egg uses under the hood so far. (Which would be the first candidate to switch. ;-) Thanks. It looks like the egg doesn't specify a test dependency on the test egg, which is used by the test suite: Error: (import) during expansion of (import ...) - cannot import from undefined module: test All the best. Mario ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] new egg: simple-timer
Hi Jörg, On 24 Nov 2018 21:59:08 +0100 Jörg F. Wittenberger wrote: > I packages a new new: simple-timer > > https://raw.githubusercontent.com/0-8-15/simple-timer/master/simple-timer.release-info > > This is intended as the one-stop shopping for low level plumping of > the background threads every other egg needs to put at the core's > timeout queue. (Either because it needs roughly correct time signals > or evade false deadlock detection.) > > I hope this could help with is the hell of reasoning about the timeout > queue in an application using several such eggs at the same time: At > least the boring timeouts are under a single umbrella. > > Right now it is just the code the `forcible` egg uses under the hood > so far. (Which would be the first candidate to switch. ;-) Thanks. It looks like the egg doesn't specify a test dependency on the test egg, which is used by the test suite: Error: (import) during expansion of (import ...) - cannot import from undefined module: test All the best. Mario -- http://parenteses.org/mario ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] new egg: simple-timer
Hi all, I packages a new new: simple-timer https://raw.githubusercontent.com/0-8-15/simple-timer/master/simple-timer.release-info This is intended as the one-stop shopping for low level plumping of the background threads every other egg needs to put at the core's timeout queue. (Either because it needs roughly correct time signals or evade false deadlock detection.) I hope this could help with is the hell of reasoning about the timeout queue in an application using several such eggs at the same time: At least the boring timeouts are under a single umbrella. Right now it is just the code the `forcible` egg uses under the hood so far. (Which would be the first candidate to switch. ;-) Best Regards /Jörg ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
