From: Gary Houston <ghouston@arglist.com>
Cc: guile-devel@gnu.org
Subject: Re: scm_def_{in,out,err}p
Date: 13 Apr 2002 22:23:19 +0100 [thread overview]
Message-ID: <200204132123.OAA29131@onyx.he.net> (raw)
In-Reply-To: <20020413142532.A26248@kiwi.pyrotechnics.com> (message from Christopher Cramer on Sat, 13 Apr 2002 14:25:32 -0500)
> From: Christopher Cramer <crayc@pyro.net>
> Date: Sat, 13 Apr 2002 14:25:32 -0500
> In root.h, there are declarations for 7 ports, that exist for every
> thread:
>
> SCM cur_inp;
> SCM cur_outp;
> SCM cur_errp;
> SCM def_inp;
> SCM def_outp;
> SCM def_errp;
> SCM cur_loadp;
>
> and then macros to access them:
>
> #define scm_cur_inp (scm_root->cur_inp)
> #define scm_cur_outp (scm_root->cur_outp)
> #define scm_cur_errp (scm_root->cur_errp)
> #define scm_def_inp (scm_root->def_inp)
> #define scm_def_outp (scm_root->def_outp)
> #define scm_def_errp (scm_root->def_errp)
> #define scm_cur_loadp (scm_root->cur_loadp)
>
> The purpose of scm_cur_* is obvious, but what are scm_def_*
> for? The only place they are used is in init.c, and there they
> are only written to. They also don't seem to be documented
> anywhere (not in the manual, or in any comments, changelogs,
> NEWS, or README).
They are inherited from SCM, where they are used in the readline
interface. Since they aren't used in Guile, I guess I'll delete
them in 1.7.0.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2002-04-13 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-13 19:25 scm_def_{in,out,err}p Christopher Cramer
2002-04-13 21:23 ` Gary Houston [this message]
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=200204132123.OAA29131@onyx.he.net \
--to=ghouston@arglist.com \
--cc=guile-devel@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).