kicad-developers team mailing list archive

[Lorenzo Marcantonio <l.marcantonio@xxxxxxxxxxxxx>]

On Fri, Dec 18, 2015 at 12:00:58AM -0500, Mark Roszko wrote:

> is just extremely silly and extra work compared to generate SEXPR
> trees in memory like SEXPR represents in the first place. God forbid
> you accidentally format that double wrong.

D'oh you actually want a full in-memory tree representation.. the full
lisp way (made of cons cells, obviously :D)

> Namely file size savings and sanity. Instead of all those ridiculous X

Well these are trivial IMHO. The biggest horror for me is splitting one
object in many data forms. I couldn't care less if the result is (data
aa bb cc) or (data "asdf==")... of course the second one is better. Even
better if you tagged it with a macro character like (data {asdf==}) so
that the reader could know that {} denotes a base64 encoded blob (the {}
is not lisp, in the '80 there was no base64 :P).

-- 
Lorenzo Marcantonio
CZ Srl - Parma