unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Olivier Dion via General Guile related discussions <guile-user@gnu.org>
To: Greg Troxel <gdt@lexort.com>, Maxime Devos <maximedevos@telenet.be>
Cc: Olivier Dion via General Guile related discussions
	<guile-user@gnu.org>,
	Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Subject: Re: [ANN] Guile-Parallel 1.0.0 released
Date: Mon, 02 Jan 2023 18:56:35 -0500	[thread overview]
Message-ID: <87edscpk24.fsf@laura> (raw)
In-Reply-To: <87h6x8pr2s.fsf@laura>

On Mon, 02 Jan 2023, Olivier Dion via General Guile related discussions <guile-user@gnu.org> wrote:
> On Mon, 02 Jan 2023, Greg Troxel <gdt@lexort.com> wrote:
>> Maxime Devos <maximedevos@telenet.be> writes:
>>
>>>> epoll is as I understand it linux only so that's not a reasonable
>>>> dependency.   fibers now works with libevent which wraps multiple
>>>> faclilities and is thus pretty portable.
>>>
>>> Guile-Fibers still uses epoll on Linux, on other systems it uses libevent.
>>
>> Understood - I just meant that fibers is now (at least 99% of the way)
>> to "broadly portable".
>>
>> I don't know the details of Olivier's question and libevent, but would
>> suggest that libevent does the sort of things that are needed and is the
>> standard portable approach and is thus worth a hard look as the
>> presumptive right answer, absent something better that only relies on
>> what POSIX requires (and what's on Hurd :-).
>
> Hmm from a description I see on Guix, libev has relative timers.  I
> don't know if it's portable like libevent though.  Will look at both
> thanks!

Well from my reading, it might be interesting to have a guile-libev.

-- 
Olivier Dion
oldiob.dev



  reply	other threads:[~2023-01-02 23:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-31  3:55 [ANN] Guile-Parallel 1.0.0 released Olivier Dion via General Guile related discussions
2022-12-31  9:06 ` Damien Mattei
2022-12-31 19:58 ` Zelphir Kaltstahl
2022-12-31 20:31   ` Olivier Dion via General Guile related discussions
2023-01-02 16:13     ` Greg Troxel
2023-01-02 17:59       ` Maxime Devos
2023-01-02 20:45         ` Greg Troxel
2023-01-02 21:24           ` Olivier Dion via General Guile related discussions
2023-01-02 23:56             ` Olivier Dion via General Guile related discussions [this message]
2023-01-03 10:57               ` Damien Mattei
2023-01-03 21:40                 ` guile-fibers timerfd_create bug (was: Re: [ANN] Guile-Parallel 1.0.0 released) Maxime Devos
2023-01-03 22:38                   ` Damien Mattei
2023-01-03 22:43                     ` Maxime Devos
2023-01-04  1:28                     ` Olivier Dion via General Guile related discussions
2023-01-03 22:06                 ` [ANN] Guile-Parallel 1.0.0 released Olivier Dion via General Guile related discussions
2023-01-03 22:29                   ` Damien Mattei
2023-01-02 20:28       ` Olivier Dion via General Guile related discussions
2023-01-08 13:30     ` Zelphir Kaltstahl
2023-01-08 14:44       ` Olivier Dion via General Guile related discussions
2023-01-08 15:17         ` Zelphir Kaltstahl
2023-01-08 15:55           ` Olivier Dion via General Guile related discussions
2023-01-08 15:59             ` Zelphir Kaltstahl
  -- strict thread matches above, loose matches on Subject: below --
2023-01-03 16:47 dsmich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87edscpk24.fsf@laura \
    --to=guile-user@gnu.org \
    --cc=gdt@lexort.com \
    --cc=maximedevos@telenet.be \
    --cc=olivier.dion@polymtl.ca \
    --cc=zelphirkaltstahl@posteo.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).