Libxo bugs and fixes.

[Phil Shafer]

"Simon J. Gerraty" writes:
>Calling flush for every xo_* call would seem like a bad idea no?

Yup, so callers would need to set the XOF_FLUSH flag by hand if
they want this odd behavior.

>The app/caller is the only one to know when a suitable flush point has
>been reached (if necessary).  
>
>It should suffice if xo_flush() does what the name implies.

Cool.  Then I'm done ;^)

>If someone is using something other than stdio for a handle, they just
>need to tell libxo a function to call in response to xo_flush ?

Exactly.  Or just flush it themselves in their write function,
if they needed an immediate flushing model.

>Does it need to be more complicated than that?

Nope.

Thanks,
 Phil