why is GPG_ERR_SEXP_ZERO_PREFIX an error for gcry_sexp_canon_len()?

[Werner Koch]

On Fri, 17 May 2019 01:59, dkg at fifthhorseman.net said:
> Hm, i don't see this text on that webpage at all.  Can you tell me where
> you're getting it from?

Second heading ("References and Documentarion"), first line:

SEXP 1.0 guide (text) --> http://people.csail.mit.edu/rivest/Sexp.txt

> But the choice gcrypt makes is also inconsistent with this list -- why
> say "no empty octet-strings" but not "no empty lists", for example?

Because it has been implemented in this way 17 years ago and any changes
now may result in broken applications.


Shalom-Salam,

   Werner


-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gcrypt-devel/attachments/20190521/a7fcb70a/attachment-0001.sig>