|
From: | John Cowan |
Subject: | Re: [Chicken-hackers] [PATCH] Move port procedures out of toplevel and drop most "chicken" imports |
Date: | Thu, 25 Jan 2018 17:49:17 -0500 |
The following procedures, however, are now in chicken.base instead:
get-output-string, open-input-string, open-output-string, port?
input-port-open?, output-port-open?, and flush-output. I've done this to
more closely match the R7RS library layout, which has those first six
procedures in scheme.base, as well as flush-output-port, which
corresponds to our flush-output. Incidentally, we might want to rename
our procedure to match.
I wasn't totally sold on port?, actually, so I put it in chicken.base
since that's what the R7RS does, and that's also where many of the other
type predicates for built-ins have gone, e.g. fixnum? and promise?.
[Prev in Thread] | Current Thread | [Next in Thread] |