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

Re: [PATCH] (Bite-size) issue #613: "svn_fs__next_key() should publish a size for users"

From: Daniele Nicolodi <daniele_at_grinta.net>
Date: 2002-08-04 18:39:58 CEST

On Sun, Aug 04, 2002 at 05:34:41PM +0100, Gareth McCaughan wrote:

> +/* The alphanumeric keys passed in and out of svn_fs__next_key
> + are guaranteed never to be longer than this many bytes,
> + *including* the trailing null byte. It is therefore safe
> + to declare a key as "char key[SVN_FS__MAX_KEY_SIZE]".
> + This will be a problem if the number of representations
> + in a filesystem ever exceeds
> + 18217977168218728251394687124089371267338971528174
> + 76066745969754933395997209053270030282678007662838
> + 67331479599455916367452421574456059646801054954062
> + 15017704234999886990788594743994796171248406730973
> + 80736524850563115569208508785942830080999927310762
> + 50733948404739350551934565743979678824151197232629
> + 947748581376,
> + but that's a risk we'll live with for npw. */
> +#define SVN_FS__MAX_KEY_SIZE 200
                                            ^^^

I think that this is a typo :-)

Ciao

-- 
Daniele
		    --- http://www.grinta.net ---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Aug 4 18:40:42 2002

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.