Hi Ludo,
2) Write a seperate elisp reader, possibly in Scheme (but could be C
as well if that's important for performance). This helps us keep
"both" readers clean and seperate, but all has to be done from ground
up and the code is probably slower (when written in Scheme).
This sounds like the
Daniel Kraft writes:
>>> 2) Write a seperate elisp reader, possibly in Scheme (but could be C
>>> as well if that's important for performance). This helps us keep
>>> "both" readers clean and seperate, but all has to be done from ground
>>> up and the code is probably slower (when written in Sch
Hi Ludo,
Ludovic Courtès wrote:
Sorry for the late reply.
no problem, thanks for the reply! I had a lot of other stuff to do
anyways, and so didn't really get into the situation of waiting for a
reply here ;)
2) Write a seperate elisp reader, possibly in Scheme (but could be C
as well if
Hi Daniel,
Sorry for the late reply.
Daniel Kraft writes:
> 2) Write a seperate elisp reader, possibly in Scheme (but could be C
> as well if that's important for performance). This helps us keep
> "both" readers clean and seperate, but all has to be done from ground
> up and the code is proba
Hi Andy and all,
as the main elisp compiler gets more and more complete (well, still a
lot details missing as well as probably even most built-ins, but
anyways), I think I'll also work on a real elisp reader (currently,
Guile's Scheme reader is used) as well as some (internals) documentation
