This is the mail archive of the
guile@cygnus.com
mailing list for the Guile project.
strports
- To: guile@sourceware.cygnus.com
- Subject: strports
- From: Eric Moore <moore@lovecraft.chem.cmu.edu>
- Date: Sat, 03 Jul 1999 21:05:58 -0400
So I was habing some problems with scwm, and I tracked them down to
some problems with string ports. One was a bug in strport.c (patch
included) the other is a more conceptual question. In scwm they use
string ports in a couple places, and wind up using various internals
in order to use them. What they're using them for is to redirect
stadard input/error/output, and in any case, it seems it'd be handy to
have a c-level function for getting the string out of a strport, maybe
for 1.4 so scwm can use it then :)
Which also leads me to ask, why in strports.c does the code use two
different methods to perform this function? Looks a little odd to me.
-Eric
Patch: (cvs diff -u strports.c)
Index: strports.c
===================================================================
RCS file: /egcs/carton/cvsfiles/guile/guile-core/libguile/strports.c,v
retrieving revision 1.21
diff -u -r1.21 strports.c
--- strports.c 1999/06/12 17:26:34 1.21
+++ strports.c 1999/07/04 00:59:51
@@ -247,7 +247,7 @@
port = scm_mkstrport (SCM_MAKINUM (0), str, SCM_OPN | SCM_WRTNG, "scm_strprint_obj");
scm_prin1 (obj, port, 1);
{
- scm_port *pt = SCM_PTAB_ENTRY (obj);
+ scm_port *pt = SCM_PTAB_ENTRY (port);
SCM answer;
answer = scm_makfromstr (SCM_CHARS (SCM_STREAM (port)),