Hi Alex,

> database file number is encoded in a kind of hexadecimal number, which
> uses @, A, B .. O instead of 0, 1, 2, .. F. The object ID is encoded in
> octal. This has the advantage that the dash '-' as a separator is not
> needed any more, because the file number digits 0 .. 7 are different
> from the letters A .. O. With that, an object might look like {1},
> {123}, {A45}, {CDE7654321} and so on.

why do you need to mix hexadecimal and octal?  I imagine having the
second part in hex would be possible too.  E.g. using 0-F for the
second part and G.. for the first would work too and the names would
be shorter?


UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Reply via email to