Replacement of Guile's garbage collector

An up to date and online version of SICP, also available in PDF and epub format

cross-posted from: https://lemmy.ml/post/29897788

LucidPlan proudly announces version v0.4.0 of the project:

https://codeberg.org/jjba23/lucidplan

#foss #project #management for everyone ( #selfhosting )

work more #agile in your team thanks to a fast-paced no-nonsense-workflow and customizability, also thanks to being written in #lisp ( #guile #scheme ) and using #guix

This tool results of years of experience using proprietary systems like Jira/Trello, and experiencing the frustrations they bring.

find my live instance here:

https://lucidplan.jointhefreeworld.org/tickets/sss

fjärrinlägg från: https://lemmy.zip/post/28653528

I got my Emacs setup fully functional and now I'm doing a little bit of hacking on my config files. (Because that's what you do on Christmas eve, when the children has fallen asleep.)

However, even though I use Geiser and fancy rainbow parentheses (plus extra Christmas bling), I run into these stupid invalid specifier errors. And the compiler output is neither pretty nor helpful. It basically gives me a large chunk of unformatted code and says there's an invalid specifier somewhere.

Questions:

Is it possible to make Guile do a pretty print on the error output?

Is it possible to make Guile error messages more precise about the problem?

He introduces but also criticizes the use of call/cc, 1. not being a function and looks like a function, 2. able to produce an union of types with it.

Is he correct? What do you think?

With Chez Scheme venturing into a compiler stack, Guile the GOTO helper, and OS infrastructure, Racket teaching, and Gambit continued awesomeness. What is left to Scheme to scheme?

You have one hour no more.