Ludovic Courtès <l...@gnu.org> writes: > Hi, > > Liliana Marie Prikler <liliana.prik...@gmail.com> skribis: > >> I think we would probably want to improve on this end in the guile- >> gcrypt module, i.e. have a public-key "constructor" that returns a >> canonical-sexp and so on. WDYT? > > I don’t find it very compelling given there’s already > ‘sexp->canonical-sexp’ & co. WDYT?
Well, the issue here is 'knowing' what sexp to pass along to that function in the first place. Are Liliana & I missing something obvious here? I had to take a string representation of a valid canonical-sexp, and pass it through string->canonical-sexp and canonical-sexp->sexp. It's definitely not an issue for managing my local configuration, but it seems silly to force _anyone_ wanting to write a canonical-sexp as a sexp through this REPL adventure, for each kind of canonical-sexp. - Jelle
