From: Christopher Cramer <crayc@pyro.net>
Subject: scm_def_{in,out,err}p
Date: Sat, 13 Apr 2002 14:25:32 -0500 [thread overview]
Message-ID: <20020413142532.A26248@kiwi.pyrotechnics.com> (raw)
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).
--
Christopher Cramer <crayc@pyro.net> <http://www.pyro.net/~crayc/>
Quoi que vous fassiez, écrasez l'infâme, et aimez qui vous aime.
-- Voltaire
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2002-04-13 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-13 19:25 Christopher Cramer [this message]
2002-04-13 21:23 ` scm_def_{in,out,err}p Gary Houston
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=20020413142532.A26248@kiwi.pyrotechnics.com \
--to=crayc@pyro.net \
/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).