unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Mikael Djurfeldt <mikael@djurfeldt.com>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: Difference between pipes and ports
Date: Wed, 11 Aug 2021 05:16:40 +0200	[thread overview]
Message-ID: <CAA2Xvw+GqSGP7mtEp_oGYX0Bznc4osrAd541-S3mqBkr1+fY_Q@mail.gmail.com> (raw)
In-Reply-To: <1c1789ba-68af-66b7-445c-333f02d89392@posteo.de>

Hi Zelphir!

A port is a scheme level concept which represents input and output devices.

Stdin, stdout and stderr are file descriptors which is an OS level concept.

A pipe is also an OS level concept. It is a communication stream between
two processes. In the OS, it is represented as a file descriptor once
opened.

The function open-input-pipe creates a child process and opens a pipe from
it. In the OS, the pipe is represented as a file descriptor. This is
represented as a port at the scheme level.

In Guile, this port also has some extra information: It has a type, #{read
pipe}, and also carries (i believe) some extra information, such as the
process identifier of the child process.

Best regards,
Mikael

Den ons 11 aug. 2021 03:14Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
skrev:

> Hello Guile users,
>
> I recently came across
> https://www.draketo.de/software/guile-capture-stdout-stderr.html
> <https://www.draketo.de/software/guile-capture-stdout-stderr.html> and
> wrote a
> commented version at
>
> https://notabug.org/ZelphirKaltstahl/guile-examples/src/master/input-output/stdout-stderr.scm
> <
> https://notabug.org/ZelphirKaltstahl/guile-examples/src/master/input-output/stdout-stderr.scm
> >.
>
> While looking at the code, I was starting to wonder, what the difference
> between
> a pipe and a port is. The reference manual does not say much about any
> definition of what a pipe is at
> https://www.gnu.org/software/guile/manual/html_node/Pipes.html
> <https://www.gnu.org/software/guile/manual/html_node/Pipes.html> and pipe
> procedure return values are also named port.
>
> However, in the REPL, they look not the same:
>
> ~~~~
> scheme@(guile-user)> (import (ice-9 popen))
> scheme@(guile-user)> (open-input-pipe "ls -al")
> $2 = #<input: #{read pipe}# 13>
> ~~~~
>
> And here for ports:
>
> ~~~~
> scheme@(guile-user)> (call-with-output-string
>                        (λ (port)
>                          (display port)))
> #<output: file 7fa2a99471c0>$6 = ""
> ~~~~
>
> Is a pipe just a special kind of port? Does it wrap a port? Or is it
> perhaps
> merely a different terminology used in different contexts in the reference
> manual?
>
> Best regards,
> Zelphir
>
> --
> repositories: https://notabug.org/ZelphirKaltstahl
>
>
>


  reply	other threads:[~2021-08-11  3:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11  1:14 Difference between pipes and ports Zelphir Kaltstahl
2021-08-11  3:16 ` Mikael Djurfeldt [this message]
2021-08-11  9:48   ` Zelphir Kaltstahl

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=CAA2Xvw+GqSGP7mtEp_oGYX0Bznc4osrAd541-S3mqBkr1+fY_Q@mail.gmail.com \
    --to=mikael@djurfeldt.com \
    --cc=guile-user@gnu.org \
    --cc=zelphirkaltstahl@posteo.de \
    /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).