Live data from Hacker News

Show HN: An implementation of Common Lisp in development, reached version 1.6

savannah.nongnu.org

1–4 of 4 posts

Show HN: An implementation of Common Lisp in development, reached version 1.6

#1
It reached version 1.6, now it covers more than 80% of the standard. alisp ships with ASDF and is capable of loading many real-world systems, let me know if your favorite system succeeds! License is GPL3 or later, no LLMs used.

Show HN: An implementation of Common Lisp in development, reached version 1.6
savannah.nongnu.org

Re: Show HN: An implementation of Common Lisp in development, reached version 1.6

#2
That's cool. I wonder how you manage to keep track of everything with this huge all-in-one main.c. Do you plan to achieve 100%? Is there a list of what is actually missing and which relevant projects depend on the missing parts? What are the core benefits compared to e.g. ECL or CLISP?

Re: Show HN: An implementation of Common Lisp in development, reached version 1.6

#3
post #2

That's cool. I wonder how you manage to keep track of everything with this huge all-in-one main.c. Do you plan to achieve 100%? Is there a list of what is actually missing and which relevant projects depend on the missing parts? What are the core benefits compared to e.g. ECL or CLISP?

> I wonder how you manage to keep track of everything with this huge all-in-one main.c

To me it's not different from having multiple files, on the contrary it's even easier to do search and replace

> Do you plan to achieve 100%?

Yes!

> Is there a list of what is actually missing and which relevant projects depend on the missing parts?

Yes, a partial list is in "Known bugs and limitations" in NOTES.

> What are the core benefits compared to e.g. ECL or CLISP?

Well, the code base is smaller and (arguably) easier to read. Building is easier. There's a debugger with stepping, very easy to use

Re: Show HN: An implementation of Common Lisp in development, reached version 1.6

#4
post #2

That's cool. I wonder how you manage to keep track of everything with this huge all-in-one main.c. Do you plan to achieve 100%? Is there a list of what is actually missing and which relevant projects depend on the missing parts? What are the core benefits compared to e.g. ECL or CLISP?

> I wonder how you manage to keep track of everything with this huge all-in-one main.c To me it's not different from having multiple files, on the contrary it's even easier to do search and replace > Do you plan to achieve 100%? Yes! > Is there a list of what is actually missing and which relevant projects depend on the missing parts? Yes, a partial list is in "Known bugs and limitations" in NOTES. > What are the cor…

Amazing work, thanks.