From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: dsmich@roadrunner.com Newsgroups: gmane.lisp.guile.devel Subject: Re: MIssing scm_memory_error Date: Mon, 10 Feb 2020 00:08:27 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=_d82b015a1cdcc6019cbc25221baa1f3a" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="52403"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 'Guile Devel' To: "'=?UTF-8?B?THVkb3ZpYyBDb3VydMOocw==?='" Original-X-From: guile-devel-bounces+guile-devel=m.gmane-mx.org@gnu.org Mon Feb 10 01:08:44 2020 Return-path: Envelope-to: guile-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1j0wd1-000DZw-8d for guile-devel@m.gmane-mx.org; Mon, 10 Feb 2020 01:08:43 +0100 Original-Received: from localhost ([::1]:55408 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j0wcz-0004Nb-U2 for guile-devel@m.gmane-mx.org; Sun, 09 Feb 2020 19:08:41 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56797) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j0wcp-0004NR-In for guile-devel@gnu.org; Sun, 09 Feb 2020 19:08:32 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j0wco-0002Z2-A1 for guile-devel@gnu.org; Sun, 09 Feb 2020 19:08:31 -0500 Original-Received: from p-impout010aa.msg.pkvw.co.charter.net ([47.43.26.141]:37256 helo=p-impout001.msg.pkvw.co.charter.net) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1j0wco-0002WD-5c; Sun, 09 Feb 2020 19:08:30 -0500 Original-Received: from localhost ([54.243.7.172]) by cmsmtp with ESMTP id 0wclj32R4vUY10wcljzxA8; Mon, 10 Feb 2020 00:08:28 +0000 X-Authority-Analysis: v=2.3 cv=fJBHIqSe c=1 sm=1 tr=0 a=ZhHbwgLlxfPm5G22ibXkng==:117 a=ZhHbwgLlxfPm5G22ibXkng==:17 a=dSg6v7tjMxUA:10 a=doupyKFmAAAA:8 a=hZ7FnZlVZrfZ6n_IriAA:9 a=QEXdDO2ut3YA:10 a=mDV3o1hIAAAA:8 a=ObOYqgXKPMI1G73g3GwA:9 a=oA9Ov6bmEiNJuRmu:21 a=_W_S_7VecoQA:10 a=PnVOTTmvsOeot2Fdb9eX:22 a=_FVE-zBwftR9WsbkzFJk:22 a=pHzHmUro8NiASowvMSCR:22 a=xoEH_sTeL_Rfw54TyV31:22 X-Mailer: Atmail X-Originating-IP: [65.185.85.154] X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal X-CMAE-Envelope: MS4wfIeV0P7LFrzUTz/6Ov879jqxfI1rKPBsV1RGnsnpaBEHo0QMpQxFn+yJt5YVYDE79B/NofWc7m6xLJIMp8Du8+wPzxRwWn21sJdAIUGP0SB/E5xYbrb/ juJaNWZO9Xw/nHn4Fb9MxQVZdouHj5xcerkB5ssRpStDE1IuP9HiGxfvy8Z/ulxlwx4/SgeTrv57tg== X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 47.43.26.141 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane-mx.org@gnu.org Original-Sender: "guile-devel" Xref: news.gmane.io gmane.lisp.guile.devel:20408 Archived-At: --=_d82b015a1cdcc6019cbc25221baa1f3a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable =0A=0A=09Thanks!=0A=0A=09The replacement for scm_memory_error seems to b= e=0Ascm_report_out_of_memory.=0A=0A=09Maybe keep SCM_MEMORY_ERROR but ha= ve it expand to=0Ascm_report_out_of_memory instead?=0A=0A=09-Dale=0A=0A= =09-----------------------------------------From: "Ludovic Court=C3=A8s"= =0ATo: dsmich@roadrunner.com=0ACc: "Guile Devel"=0ASent: Sunday Februar= y 9 2020 6:12:43PM=0ASubject: Re: MIssing scm_memory_error=0A=0AHi Dale,= =0A=0A dsmich@roadrunner.com skribis:=0A=0A > In Guile 3.0 (and probably= earlier) scm_memory_error has gone away,=0A > with no mention of a repl= acement in NEWS.=0A=0A It would seem that =E2=80=98scm_memory_error=E2= =80=99 was deprecated in 2014 in=0Acommit=0A c2247b782a9234bb9aedee5204c= 30daf1d01a510 and removed in 2017 in=0Acommit=0A c248ea10beb2afa4c113dbc= 6dc707bed5dbfc92e.=0A=0A However, =E2=80=98SCM_MEMORY_ERROR=E2=80=99 in= =E2=80=98error.h=E2=80=99 still refers to it,=0Aand so does=0A the manu= al.=0A=0A Commit 1a3e316c32562aec2665a0233d46d5635f9c1245 fixes that by= =0Aremoving=0A all traces of =E2=80=98scm_memory_error=E2=80=99.=0A=0A T= hank you,=0A Ludo=E2=80=99.=0A --=_d82b015a1cdcc6019cbc25221baa1f3a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Thanks!

The replacement for scm_memory_error = seems to be scm_report_out_of_memory.

Maybe keep SCM_MEMORY_E= RROR but have it expand to scm_report_out_of_memory instead?


<= /p>

-Dale



=

-----------------------------------------

From: "Ludovic Cou= rt=C3=A8s"
To: dsmich@roadrunner.com
Cc: "Guile Dev= el"
Sent: Sunday February 9 2020 6:12:43PM
Subject: Re: MIssing sc= m_memory_error

Hi Dale,
=0A
=0Adsmich@roadrunner.com skribi= s:
=0A
=0A> In Guile 3.0 (and probably earlier) scm_memory_erro= r has gone away,
=0A> with no mention of a replacement in NEWS.=0A
=0AIt would seem that =E2=80=98scm_memory_error=E2=80=99 was dep= recated in 2014 in commit
=0Ac2247b782a9234bb9aedee5204c30daf1d01a510= and removed in 2017 in commit
=0Ac248ea10beb2afa4c113dbc6dc707bed5db= fc92e.
=0A
=0AHowever, =E2=80=98SCM_MEMORY_ERROR=E2=80=99 in =E2= =80=98error.h=E2=80=99 still refers to it, and so does
=0Athe manual.=
=0A
=0ACommit 1a3e316c32562aec2665a0233d46d5635f9c1245 fixes that= by removing
=0Aall traces of =E2=80=98scm_memory_error=E2=80=99.
= =0A
=0AThank you,
=0ALudo=E2=80=99.
=0A --=_d82b015a1cdcc6019cbc25221baa1f3a--