From: Olivier Dion via General Guile related discussions <guile-user@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>, guile-user@gnu.org
Subject: Re: Using Guile 2.2 modules with Guile 3
Date: Sat, 06 Aug 2022 11:31:15 -0400 [thread overview]
Message-ID: <871qtt4ce4.fsf@laura> (raw)
In-Reply-To: <28582fb6-8134-a1d8-9bfb-2dc14c5e0ede@telenet.be>
On Sat, 06 Aug 2022, Maxime Devos <maximedevos@telenet.be> wrote:
> On 06-08-2022 17:11, Olivier Dion via General Guile related discussions
> wrote:
>> Hi,
>>
>> Say I want to use guile-dbi wich use Guile 2.2. Is there any danger for
>> me to use it with Guile 3.0? I see that Guile will recompile the module
>> because the already compiled one does not match, I guess. Other than
>> that, any side effects?
>>
>> Regards,
>> old
>>
> Going by the package definition, guile-dbd-postgresql seems to make a
> Guile extension (C). There have been incompatible changes (both on the
> Guile code level, and presumably on the C level). As such, sounds risky
> to me.
>
> Also, for whatever reason, guile-dbi propagates an old guile, so you'll
> get a propagation conflict without guarantees on which Guile version ‘wins’.
>
So I guess it would be better for me to use something like guile-sqlite3.
--
Olivier Dion
oldiob.dev
next prev parent reply other threads:[~2022-08-06 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 15:11 Using Guile 2.2 modules with Guile 3 Olivier Dion via General Guile related discussions
2022-08-06 15:29 ` Maxime Devos
2022-08-06 15:31 ` Olivier Dion via General Guile related discussions [this message]
2022-08-06 15:36 ` Maxime Devos
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=871qtt4ce4.fsf@laura \
--to=guile-user@gnu.org \
--cc=maximedevos@telenet.be \
--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).