Re: Copyright assignment

[Axel Forsman]

Eshel Yaron <me@eshelyaron.com> writes:

> Your conversion maps
> Erlang atoms to Elisp symbols, and AFAICT it will happily map the atom
> nil to the symbol nil, while in the other direction (Elisp to Erlang),
> nil is mapped to the empty list.  That means that the Erlang improper
> list [foo|nil] maps to the proper Elisp list (foo) which then maps to
> the proper Erlang list [foo].

Yup, I am aware that this is something that will have to be fixed eventually.
However, for now I do not foresee it being too much of a problem in practice,
since, in my experience, nil is not used as an atom much
in favor of undefined/false/error/etc.


Thanks for taking a look
Axel