LOCATION calling procedure/context id
NAME name for the port (usually the process command pathname)
FILENO open file descriptor
BUFFER-INFO either a fixnum size or a string
ON-CLOSE fileno was closed notification procedure
MORE-PREDICATE boolean procedure indicating whether more input is
available, usually not needed but the programmer may know something
that the C 'read' procedure doesn't
Interesting... Let me put forward the following proposal:
1. Binary streams, maybe wrapping fread / fwrite.
2. Two stream APIs (one for binary and one for char ports)
The ideea would be that I'd be able to write, for example, my own
application-level reliable transport protocol over UDP, and wrap it into
Chicken Streams. The char output stream API could look like
(##sys#make-output-stream write-char close)
and the input one
(##sys#make-input stream peek-char read-char close)
This, of course, doesn't yet take into account threads and UTF8.
What do you guys think?
_______________________________________________
Chicken-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/chicken-users
