[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: RFC: building eol and encoding support into svn_stream_t

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2004-10-17 23:48:43 CEST

On Sun, 2004-10-17 at 17:39, Peter N. Lundblad wrote:
> My proposal is to add support for recoding and eol translation to our
> svn_stream_t interface.

That's not a complete proposal, but I'm -1 on it pretty much no matter
how you flesh it out, because I think stacking streams is a cleaner way
of handling the issue.

Of course, you thought of that too:

> Why not just stack a recoding stream onto an existing stream like we do
> for compression? That's because the creator of the stream knows the
> encoding it should be outputing, but the user of the stream may need to
> turn it into binary mode.

This argument doesn't make sense to me. If the user of the stream needs
to make the final decision about encoding and newlines, then the
producer should just use a specified value (UTF-8 and \n) and the
receiver can stack a recoding stream on top of it.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Oct 17 23:48:59 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.