From: Olivier Dion via General Guile related discussions <guile-user@gnu.org>
To: guile-user@gnu.org
Subject: Using Guile for soft-realtime
Date: Wed, 11 Nov 2020 23:45:56 -0500 [thread overview]
Message-ID: <87a6vnuqrf.fsf@clara> (raw)
Hi Guile's community,
I would like to use Guile as a scripting engine for a soft-realtime
software. I'm a little bit worried about the asynchronous nature of the
GC and its nondeterministic time.
Searching in the manual, I found the section 5.7.4.2 about performance
constraints, which is empty unfortunately.
Thus, does anyone had similar experiences in the past? Are my worries
even valids?
--
Olivier Dion
PolyMtl
next reply other threads:[~2020-11-12 4:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 4:45 Olivier Dion via General Guile related discussions [this message]
2020-12-28 0:55 ` Using Guile for soft-realtime Joshua Branson via General Guile related discussions
2021-01-24 16:25 ` olivier.dion--- via General Guile related discussions
2021-01-25 13:29 ` Dr. Arne Babenhauserheide
2021-01-24 19:05 ` jbranso
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=87a6vnuqrf.fsf@clara \
--to=guile-user@gnu.org \
--cc=olivier.dion@polymtl.ca \
/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).