* ptobs for Guile 2.2+
@ 2020-12-13 8:46 Thien-Thi Nguyen
2020-12-13 16:25 ` Ludovic Courtès
0 siblings, 1 reply; 3+ messages in thread
From: Thien-Thi Nguyen @ 2020-12-13 8:46 UTC (permalink / raw)
To: guile-user
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
I'm trying to upgrade Guile-PG for Guile 2.2 (and possibly 3.0).
It currently uses ptobs for the large object ("lobj") support in
libpq, mostly for buffering and buffer synchronization. I see
in libguile/ports.h (Guile 2.0.13), however:
/* Hey you! Yes you, reading the header file! We're going to
deprecate scm_ptobs in 2.2, so please don't write any new
code that uses it. Thanks. */
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?
--
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 --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: ptobs for Guile 2.2+
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
0 siblings, 1 reply; 3+ messages in thread
From: Ludovic Courtès @ 2020-12-13 16:25 UTC (permalink / raw)
To: guile-user
Hi ttn,
Thien-Thi Nguyen <ttn@gnuvola.org> skribis:
> I'm trying to upgrade Guile-PG for Guile 2.2 (and possibly 3.0).
> It currently uses ptobs for the large object ("lobj") support in
> libpq, mostly for buffering and buffer synchronization. I see
> in libguile/ports.h (Guile 2.0.13), however:
>
> /* Hey you! Yes you, reading the header file! We're going to
> deprecate scm_ptobs in 2.2, so please don't write any new
> code that uses it. Thanks. */
>
> 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. :-)
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.
HTH,
Ludo’.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: ptobs for Guile 2.2+
2020-12-13 16:25 ` Ludovic Courtès
@ 2020-12-13 17:47 ` Thien-Thi Nguyen
0 siblings, 0 replies; 3+ messages in thread
From: Thien-Thi Nguyen @ 2020-12-13 17:47 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: guile-user
[-- 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 --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-12-13 17:47 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).