unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Alex Vong <alexvong1995@gmail.com>
To: Thomas Morley <thomasmorley65@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: What's up with 'current-load-port'
Date: Wed, 07 Nov 2018 04:25:54 +0800	[thread overview]
Message-ID: <87h8guymul.fsf@gmail.com> (raw)
In-Reply-To: <CABsfGyX4QTqodAhqo2ZFEZAZk6nCfynaV838KerhvDHw_=KkSQ@mail.gmail.com> (Thomas Morley's message of "Sun, 4 Nov 2018 14:14:23 +0100")

[-- Attachment #1: Type: text/plain, Size: 489 bytes --]

Thomas Morley <thomasmorley65@gmail.com> writes:

[...]
>
> Hi Alex,
>
> thanks for the hint.
> Would a patch like attached be sufficient?
>
I am not sure. Looking into the source, in the
"Current ports as parameters" section, you can see that
'current-*-port' are being defined. They feel like some kind of wrappers
around the primitive versions defined in libguile. I don't know what are
their uses and whether we should have something similar for
'current-load-port'.

> Best,
>   Harm

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2018-11-06 20:25 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
2018-11-06 20:25     ` Alex Vong [this message]
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=87h8guymul.fsf@gmail.com \
    --to=alexvong1995@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=thomasmorley65@gmail.com \
    /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).