--- TODO 2003/01/06 16:36:59 1.2
+++ TODO 2003/01/06 19:04:56 1.3
@@ -1,8 +1,8 @@
- _ ___ ____ ____ ____ _
- |_|_ _ / _ \/ ___/ ___|| _ \ ___(_) ___
- _|_||_| | | | \___ \___ \| |_) | / __| |/ _ \
+ _ ___ ____ ____ ____ _
+ |_|_ _ / _ \/ ___/ ___|| _ \ ___(_) ___
+ _|_||_| | | | \___ \___ \| |_) | / __| |/ _ \
|_||_|_| | |_| |___) |__) | __/ \__ \ | (_) |
- |_|_|_| \___/|____/____/|_| |___/_|\___/
+ |_|_|_| \___/|____/____/|_| |___/_|\___/
OSSP sio - Stream I/O
@@ -34,7 +34,7 @@
SIO_XSTREAM Invoke Crossstream Stage
SIO_LOOP Loop through current Stage
- o sio.h haengt von al.h ab wegen References to al_t!
+ o sio.h haengt von al.h ab wegen References to al_t!
Suggestion: forward declaration in sio.h for al_t.
o sio_push: I expected a different operation by reading "push" here.
@@ -51,7 +51,7 @@
o sios->{open,close}{r,w}(): any reason why it's four functions
and not just two? I intuitively expected just sios->{open,close}()
with an additional parameter indicating read or write operation.
-
+
o sio_configure_stage is unneccesary restrictive in passed data:
< sio_rc_t sio_configure_stage(sio_t *sio, sio_stage_t *sios, void *o, void *v);
> sio_rc_t sio_configure_stage(sio_t *sio, sio_stage_t *sios, void *v, ...);
@@ -59,7 +59,7 @@
> sio_rc_t (*configure) (sio_t *, void *, void *, va_list ap);
This way the application can decide itself how it is configured
and with which parameter stypes and with how much parameters.
-
+
o Additionally to make sios->configure implementations easier and to
reduce complexity and redundancy, I suggest to provide a
sio_setparams() function which is similar to l2_util_setparams() in
|
