From: dsmich@roadrunner.com
To: "'Ludovic Courtès'" <ludo@gnu.org>
Cc: 'Guile Devel' <guile-devel@gnu.org>
Subject: Re: MIssing scm_memory_error
Date: Mon, 10 Feb 2020 00:08:27 +0000 [thread overview]
Message-ID: <a46af3f2a0d9c969da4922d84adf69c46868c874@webmail> (raw)
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
Thanks!
The replacement for scm_memory_error seems to be
scm_report_out_of_memory.
Maybe keep SCM_MEMORY_ERROR but have it expand to
scm_report_out_of_memory instead?
-Dale
-----------------------------------------From: "Ludovic Courtès"
To: dsmich@roadrunner.com
Cc: "Guile Devel"
Sent: Sunday February 9 2020 6:12:43PM
Subject: Re: MIssing scm_memory_error
Hi Dale,
dsmich@roadrunner.com skribis:
> In Guile 3.0 (and probably earlier) scm_memory_error has gone away,
> with no mention of a replacement in NEWS.
It would seem that ‘scm_memory_error’ was deprecated in 2014 in
commit
c2247b782a9234bb9aedee5204c30daf1d01a510 and removed in 2017 in
commit
c248ea10beb2afa4c113dbc6dc707bed5dbfc92e.
However, ‘SCM_MEMORY_ERROR’ in ‘error.h’ still refers to it,
and so does
the manual.
Commit 1a3e316c32562aec2665a0233d46d5635f9c1245 fixes that by
removing
all traces of ‘scm_memory_error’.
Thank you,
Ludo’.
[-- Attachment #2: Type: text/html, Size: 1221 bytes --]
next reply other threads:[~2020-02-10 0:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 0:08 dsmich [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-19 23:09 MIssing scm_memory_error dsmich
2020-01-19 22:48 dsmich
2020-02-09 23:12 ` Ludovic Courtès
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=a46af3f2a0d9c969da4922d84adf69c46868c874@webmail \
--to=dsmich@roadrunner.com \
--cc=guile-devel@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).