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

Re: Should svn_hash_(read|write) accept streams?

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2004-04-11 03:15:06 CEST

On Sat, 2004-04-10 at 20:56, Branko ╚ibej wrote:
> >So what are your thoughts about creating two new functions:
> >svn_hash_read2 and svn_hash_write2 that accept svn_stream_t as

> svn_hash_read_stream and svn_hash_write_stream, please. Make the
> function names mnemonic.

I think you're swimming against the tide here. We use a "2" suffix when
we're simply revving an API; we only use a new name when we've come up
with a name which is genuinely better. Since we don't normally tack
"_stream" onto the end of functions which operate on streams, this falls
into the first category.

> >input/output. The originals could be removed at the next API change.

> (and the originals can't be removed until 2.0, which is not the next API
> change :-)

He meant the next incompatible API change, which is (presumably) at 2.0.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 11 03:15:30 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.