[tor-commits] [torspec/master] Remove incorrect definition of lexical order.

[nickm@xxxxxxxxxxxxxx]

commit 460ab170f2a3ba941803f2665c24b0bcee2d9849
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date:   Mon Jul 23 12:42:59 2012 -0400

    Remove incorrect definition of lexical order.
    
    For the correct definition of lexical order, search for "lexical
    comparison".  It's what your favorite language does for string
    comparison, unless your favorite language is something really
    esoteric.
    
    In short:
        If A and B are equal at every position, they are lexically equal.
        Otherwise, if A is a prefix of B, A precedes B.
        Otherwise, let i be the first position where A differs from
          B. If A[i] precedes B[i], A precedes B.
---
 version-spec.txt |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)

diff --git a/version-spec.txt b/version-spec.txt
index 54a2ac0..4a3dccf 100644
--- a/version-spec.txt
+++ b/version-spec.txt
@@ -33,8 +33,7 @@
  release. If the tag ends with "-cvs" or "-dev", you're looking at a
  development snapshot that came after a given release.  If we *do*
  encounter two versions that differ only by status tag, we compare them
- lexically as ASCII byte strings (ie, reverse-alphabetically so 'b' comes
- before 'a'). The STATUS_TAG can't contain whitespace.
+ lexically. The STATUS_TAG can't contain whitespace.
 
  The EXTRA_INFO is also purely informational, often containing information
  about the SCM commit this version came from. It is surrounded by parentheses

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits