From: Olivier Dion via General Guile related discussions <guile-user@gnu.org>
To: Vivien Kraus <vivien@planete-kraus.eu>,
Christine Lemmer-Webber <cwebber@dustycloud.org>,
guile-user@gnu.org
Subject: Re: Newbie thoughts on Guile Hall + Guix
Date: Sun, 06 Feb 2022 17:10:05 -0500 [thread overview]
Message-ID: <877da77iki.fsf@laura> (raw)
In-Reply-To: <c7e70292be06f6020b4339608a57660471b90cfd.camel@planete-kraus.eu>
On Sun, 06 Feb 2022, Vivien Kraus <vivien@planete-kraus.eu> wrote:
> Hello,
>
> Le dimanche 06 février 2022 à 11:35 -0500, Olivier Dion via General
> Guile related discussions a écrit :
>> As much as I like hall for pure Guile project,
>> it's difficult to integrate extension libraries written in C.
>
> While this is certainly true, I think that nyacc is on the right track
> to let us use C libraries without writing a single line of C code.
I agree that when you want to use a C library that's already there, the
state of FFI in Guile is awesome. However, you sometime need to write
your own C code for low level stuffs. For example, I require C for
developing custom memory allocators, fast audio mixing with SIMD,
multi-threading with OpenMP, etc. These require many tweaks in the
build system to integrate correctly with Guile at compile and run times.
--
Olivier Dion
Polymtl
next prev parent reply other threads:[~2022-02-06 22:10 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 20:01 Newbie thoughts on Guile Hall + Guix Christine Lemmer-Webber
2022-02-05 22:15 ` Mikael Djurfeldt
2022-02-05 23:19 ` Jose Antonio Ortega Ruiz
2022-02-06 14:09 ` Ricardo Wurmus
2022-02-06 0:40 ` Christine Lemmer-Webber
2022-02-06 4:54 ` Aleix Conchillo Flaqué
2022-02-06 13:14 ` Mikael Djurfeldt
2022-02-06 14:03 ` Ricardo Wurmus
2022-02-06 14:28 ` Vijay Marupudi
2022-02-06 14:53 ` Ognen Duzlevski
2022-02-06 15:13 ` Maxime Devos
2022-02-06 15:29 ` Vijay Marupudi
2022-02-06 21:34 ` Zelphir Kaltstahl
2022-02-07 2:11 ` David Pirotte
2022-02-07 2:47 ` David Pirotte
2022-02-07 19:21 ` Zelphir Kaltstahl
2022-02-07 22:35 ` adriano
2022-02-05 22:16 ` Vivien
2022-02-06 2:53 ` Zelphir Kaltstahl
2022-02-06 16:35 ` Olivier Dion via General Guile related discussions
2022-02-06 16:44 ` Vivien Kraus
2022-02-06 22:10 ` Olivier Dion via General Guile related discussions [this message]
2022-02-06 16:55 ` Maxime Devos
2022-02-06 22:05 ` Olivier Dion via General Guile related discussions
2022-02-06 22:32 ` Maxime Devos
2022-02-06 23:00 ` Olivier Dion via General Guile related discussions
2022-02-06 21:37 ` Zelphir Kaltstahl
2022-02-06 22:12 ` Olivier Dion via General Guile related discussions
-- strict thread matches above, loose matches on Subject: below --
2022-02-06 13:40 dsmich
2022-02-08 12:19 Blake Shaw
2022-02-08 19:46 ` Chris Vine
2022-02-09 6:28 ` Catonano
2022-02-08 16:13 Blake Shaw
2022-02-09 3:23 Blake Shaw
2022-02-09 10:30 Blake Shaw
2022-02-09 14:13 ` Olivier Dion via General Guile related discussions
2022-02-09 20:05 ` Aleix Conchillo Flaqué
2022-02-09 20:28 ` Maxime Devos
2022-02-09 21:13 ` Aleix Conchillo Flaqué
2022-02-10 18:03 ` Vivien
2022-02-10 12:42 Blake Shaw
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=877da77iki.fsf@laura \
--to=guile-user@gnu.org \
--cc=cwebber@dustycloud.org \
--cc=olivier.dion@polymtl.ca \
--cc=vivien@planete-kraus.eu \
/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).