From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: ptobs for Guile 2.2+
Date: Sun, 13 Dec 2020 12:47:02 -0500 [thread overview]
Message-ID: <87r1ntegyx.fsf@gnuvola.org> (raw)
In-Reply-To: <874kkpzn8w.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 13 Dec 2020 17:25:51 +0100")
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
() Ludovic Courtès <ludo@gnu.org>
() Sun, 13 Dec 2020 17:25:51 +0100
> So, what do people do for "old" code that currently uses
> ptobs (i.e., for Guile 2.0 and earlier)? Is there a
> recommended migration path (besides "give up" :-D)? What
> am i missing?
Giving up sounds like a reasonable strategy to me at this
point in time. :-)
I suppose it's reasonable at any point of time. :-D
If you want to do it anyway, I know GDB and GnuTLS have port
code that deals with both 2.0 and 2.2/3.0, perhaps that can
help.
Thanks for the pointer. I'll see what i can scrounge there.
--
Thien-Thi Nguyen -----------------------------------------------
(defun responsep (query) ; (2020) Software Libero
(pcase (context query) ; = Dissenso Etico
(`(technical ,ml) (correctp ml))
...)) 748E A0E8 1CB8 A748 9BFA
--------------------------------------- 6CE4 6703 2224 4C80 7502
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 219 bytes --]
prev parent reply other threads:[~2020-12-13 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 8:46 ptobs for Guile 2.2+ Thien-Thi Nguyen
2020-12-13 16:25 ` Ludovic Courtès
2020-12-13 17:47 ` Thien-Thi Nguyen [this message]
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=87r1ntegyx.fsf@gnuvola.org \
--to=ttn@gnuvola.org \
--cc=guile-user@gnu.org \
--cc=ludo@gnu.org \
/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).