* bug#69857: ports.c, "scm-set-current-output-port" vs "set-current-output-port"
@ 2024-03-17 14:21 Matt Wette
0 siblings, 0 replies; only message in thread
From: Matt Wette @ 2024-03-17 14:21 UTC (permalink / raw)
To: 69857
In guile-3.0.9, in ports.c I believe scheme name for setting the error
output is
inappropriately named "scm-set-current-output-port". It does not show
in guile
because set-current-output-port is defined using the parameter
current-output-port.
SCM
scm_set_current_input_port (SCM port)
#define FUNC_NAME "set-current-input-port"
{
...
}
#undef FUNC_NAME
SCM
scm_set_current_output_port (SCM port)
#define FUNC_NAME "scm-set-current-output-port"
{
...
}
#undef FUNC_NAME
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2024-03-17 14:21 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-03-17 14:21 bug#69857: ports.c, "scm-set-current-output-port" vs "set-current-output-port" Matt Wette
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).