Sexp changes between 1.5.3 and 1.6.0

Werner Koch wk at
Sat Dec 21 20:24:41 CET 2013

On Sat, 21 Dec 2013 12:42, ludo at said:

>   1. ‘gcry_sexp_sprint’, in GCRYSEXP_FMT_ADVANCED mode, renders the
>      sexp ‘#C0FFEE#’ as ‘#C0FFEE#’ with 1.6, but as a binary byte
>      sequence in 1.5.

Right, I changed the heuristics to better cope with the data we are
commonly using with Libgcrypt.

>   2. ‘gcry_sexp_nth (a (b 3:pqr) (c 3:456) (d 3:xyz)) 0’ returns the
>      complete list in 1.5, whereas in 1.6 it returns NULL (which makes
>      more sense IMO.)

Are you sure, that it was wrong 1.5?  A quick check does not reveal code
changes.  But there might have been changes creating the sexp in the
first place.



Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.

More information about the Gcrypt-devel mailing list