From: Thomas Morley <thomasmorley65@gmail.com>
To: alexvong1995@gmail.com
Cc: guile-user@gnu.org
Subject: Re: What's up with 'current-load-port'
Date: Sun, 4 Nov 2018 14:14:23 +0100 [thread overview]
Message-ID: <CABsfGyX4QTqodAhqo2ZFEZAZk6nCfynaV838KerhvDHw_=KkSQ@mail.gmail.com> (raw)
In-Reply-To: <87zhupxb04.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
Am So., 4. Nov. 2018 um 13:50 Uhr schrieb Alex Vong <alexvong1995@gmail.com>:
>
> Hello,
>
> Thomas Morley <thomasmorley65@gmail.com> writes:
>
> > Hi,
> >
> > what's up with 'current-load-port'?
> >
> > Simply checking in a guile-prompt I get:
> > guile-1.8: #<primitive-procedure current-load-port>
> > guile-2.0.14: #<procedure current-load-port ()>
> > guile-2.2.4 and guile-2.9.1:
> > ;;; <unknown-location>: warning: possibly unbound variable `current-load-port'
> > ERROR: In procedure module-lookup: Unbound variable: current-load-port
> >
> > It's in the manual, though, without any hint it could be deprecated or
> > disabled or the need to use a certain module.
> >
> > What am I missing?
> >
> Indeed, looking at the (ice-9 ports) module. It seems the
> 'current-load-port' procedure is not exported for some reason
> (forgotten?). A workaround would be to resolve it directly:
>
> (@@ (ice-9 ports) current-load-port)
>
> >
> > Cheers,
> > Harm
>
> Cheers,
> Alex
Hi Alex,
thanks for the hint.
Would a patch like attached be sufficient?
Best,
Harm
[-- Attachment #2: 0001-Export-current-load-port-from-ice-9.patch --]
[-- Type: text/x-patch, Size: 752 bytes --]
From 6f85349c6a1353023b06c64985bc59397d9b8bc4 Mon Sep 17 00:00:00 2001
From: Thomas Morley <thomasmorley65@gmail.com>
Date: Sun, 4 Nov 2018 14:10:38 +0100
Subject: [PATCH] Export current-load-port from ice-9
---
module/ice-9/ports.scm | 1 +
1 file changed, 1 insertion(+)
diff --git a/module/ice-9/ports.scm b/module/ice-9/ports.scm
index 8eee22988..061ae1c27 100644
--- a/module/ice-9/ports.scm
+++ b/module/ice-9/ports.scm
@@ -30,6 +30,7 @@
%port-property
%set-port-property!
current-input-port current-output-port
+ current-load-port
current-error-port current-warning-port
set-current-input-port set-current-output-port
set-current-error-port
--
2.17.1
next prev parent reply other threads:[~2018-11-04 13:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 11:55 What's up with 'current-load-port' Thomas Morley
2018-11-04 12:50 ` Alex Vong
2018-11-04 13:14 ` Thomas Morley [this message]
2018-11-06 20:25 ` Alex Vong
2018-11-05 1:43 ` Mark H Weaver
2018-11-05 8:25 ` Thomas Morley
2018-11-05 9:49 ` Thomas Morley
2018-11-05 10:14 ` Ludovic Courtès
2018-11-05 23:37 ` Thomas Morley
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='CABsfGyX4QTqodAhqo2ZFEZAZk6nCfynaV838KerhvDHw_=KkSQ@mail.gmail.com' \
--to=thomasmorley65@gmail.com \
--cc=alexvong1995@gmail.com \
--cc=guile-user@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).