why is GPG_ERR_SEXP_ZERO_PREFIX an error for gcry_sexp_canon_len()?

[Werner Koch]

On Tue, 14 May 2019 16:56, dkg at fifthhorseman.net said:

> Can someone who understands S-Expressions better than me point me to
> documentation that will help me understand why gcry_sexp_canon_len()
> should treat this as an error?

From the specs: http://theory.lcs.mit.edu/~rivest/sexp.html

| 10. Utilization of S-expressions
| 
| This note has described S-expressions in general form.  Application writers
| may wish to restrict their use of S-expressions in various ways.  Here are
| some possible restrictions that might be considered:
| 
| 	-- no display-hints
| 	-- no lengths on hexadecimal, quoted-strings, or base-64 encodings
| 	-- no empty lists
| 	-- no empty octet-strings


Salam-Shalom,

   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/20190515/e5898804/attachment.sig>