Re: G_SEEK_CUR and stateless iconv encodings

[rsteinke w-link net]

From: Owen Taylor <otaylor redhat com>
>
> rsteinke w-link net writes:
> >
> > 	My question is, would this be an API change? It doesn't add any
> > new functions; it only touches the header file to add a bitflag to the
> > GIOChannel structure. The rest is changes to the backend, and (still
> > unimplemented) changes to the docs. I've attached the patch below
> > for anyone who's interested. The "UTF-8 like" encodings would be
> > specified in enc_list in check_encoding_stateful().
>
> Well, it _is_ an API change, but we've snuck in some other small
> "API changes that don't change the function headers.
>
> However, but I think it's something that can easily wait until after
> 2.0. I don't think either seeking from the current position or mixing
> reads and writes is something that is going to be done very often,
> especially not on a stream with encoding conversion.
>
> I'd like to hold off on this, if you don't mind. You might want to
> file a bug in bugzilla to track the issue.

No problem. I've got a couple of things I've got waiting in the wings
for when 2.1 gets going.

Ron