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

Re: Maintaining NodeID sanity

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-05-10 22:51:12 CEST

Greg Stein <gstein@lyra.org> writes:
> But they *are* integers. That is the point behind the "next-key" stuff. An
> integer sits in there, and it gets incremented. Applying a transformation to
> that value is obscuring its origin.
> The base64 values also have an ordering (ever hear of strcmp() ?). So this
> point doesn't really seem to apply.

Um, yes, any two strings have an ordering, if you assign values to
their symbols. But we're not *using* the ordering, that's the
important thing.

(The fact that we use ordering trivially as part of the process of
generating a new unique ID is irrelevant. Call it the "next" key is
misleading: it's just a "new" key, and the method by which we
guarantee its uniqueness doesn't need to infect the rest of the code.)

> > - As a developer debugging the code, it's easier for me to
> > recognize and remember shorter strings in an alphabet with more
> > symbols, than longer strings in an alphabet with fewer symbols.
> > Long strings of numbers start to look all alike pretty quickly
> > (at least to me).
> That is FUD, too. "abcdef" and "abcdeg" look awfully the same, too.

Nah, calling it FUD is FUD :-). My statement was personal, and
completely accurate. If it's not true for you, that's great -- I
never said it was.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 10 22:52:20 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.