[
Lists Home |
Date Index |
Thread Index
]
> Right now genx does output to a FILE *. Several have suggested that it
> should do output via an abstracted callback. This sounds kind of
> seductive, and is indeed much more general, and would be no biggie to
> implement, but the more I think about it the less I like it. So at the
> moment I'm leaning to sticking with FILE * for the following reasons:
> ...
> So this would be a good time to say "I'd use genx for XXX, but if it
> sticks with FILE * I'm not going to be able to use it because of YYY".
I'd use genx for streaming XML through sockets, but it sticks with FILE *.
I'm not going to be able to use it efficiently because of the overhead
and different blocking model.
David Tolpin
|
