#r6rs — Public Fediverse posts

@wingo is asking if anyone knows of a good course on the Nanopass framework (perhaps to recommend to others), but as usual he forgot to add hashtags to his post. So please reply to this post here: https://mastodon.social/@wingo/113956474737820425

#tech #software #Lisp #Scheme #SchemeLang #R7RS #R6RS #GuileScheme #Guile #Compilers #ProgrammingLanguages #PLT

Prof. Dybvig's paper, "The Development of Chez Scheme" (2006), is a brief history of the #Chez Scheme compiler that he had been working on since 1985. Despite his quiet, understated tone, he manages to convey in this paper his heart-felt enthusiasm for, and decades-long dedication to, the Scheme language and its implementations. This is indeed an inspiration to all of us #geeks. Today, Chez Scheme is one of the fastest, most compact, and most advanced implementation of #R6RS.

https://citeseerx.ist.psu.edu/document?repid=rep1&type=pdf&doi=bee2a90e39bc709835ae184e286a20afb02a0792

Dybvig was, in turn, a student of another pillar of the Scheme community, Prof. Friedman. I first came across Dybvig's work, when I read the 1ed of his famous book, "The Scheme Programming Language" (1987), the 4ed of which was published in 2009 and it covers R6RS.

https://www.amazon.com/Scheme-Programming-Language-Kent-Dybvig/dp/013791864X

The book "Chez Scheme Version 10.0.0 User’s Guide" (2024), published by Cisco, covers the inner workings of Chez Scheme v10, which is a superset of R6RS.

https://cisco.github.io/ChezScheme/csug10.0/csug.pdf

Chez Scheme and the whole of Dybvig's work are the guide posts for all #Lisp and #Scheme #programmers.

Matthias Felleisen: #R6RS is "perfect"
https://blog.racket-lang.org/2007/06/r6rs-is-perfect.html

Despite purported borderline abusive levels of chutzpah, the man knows what he's talking about.
#scheme #lisp #racket

Dr. #Racket: Or How I Learned to Stopped to Worrying and Love #lang #r6rs

#scheme #lisp

PCI bus enumeration in #Scheme

https://gitlab.com/weinholt/loko/-/raw/master/drivers/pci.sls
#loko #r6rs #lisp #os #kernel

#r6rs #scheme we are so back

I guess what I'm trying to say is, #r6rs is the #scheme of the #smuglispweenie

Hot take: in terms of the language specified treated independently of the social process of standardization itself, everyone's beloved #r5rs is actually the worst post-#r4rs scheme, and #r6rs is easily the best and most revolutionary, hence the controversy surrounding it.

#lisp #srfi

A Realtek RTL8139 wifi driver written in #r6rs #scheme for the #loko kernel & operating system

Loko's concurrency is based on #Guile's Fibers implementation of ConcurrentML.

https://gitlab.com/weinholt/loko/-/raw/master/drivers/net/rtl8139.sls

@ramin_hal9001 the thing is, I would say this is starting to change with r6 and #r7rs implementations, and #akku does a pretty job of working out the compatibility between different implementations (but the guix package needs some fixing... on my TODOs).

but I agree about the pressure to pick the right one, it drove me mad, but I also think that the idea that getting used to multiple schemes is impossible, and it should even be encouraged to work with a few of them, because once you've navigated a couple, they're all kind of the same at root. but I think people should stick to one for their first year.

it's primarily just the #r5rs implementations that differ wildly. I think theres this mythology that r5rs was this legendary, impeccable standard, and that the process went astray after that, but the truth is that #r6rs really was a massive improvement, and r7rs-large will be something like r6rs (creating an r7rs compatability later for r6rs schemes is a matter of defining a module and a few identifier-syntax macros). problems with post-r5rs are primarily social, rather than technical imo.

@PaniczGodek oh really? to me they are like the bread and butter. when you build good records and structure your programs around them, your flexibility increases dramatically as you have these quasi-"intermediate representations" that are extensible and easy + performant to handle. many schemes use records as their fundamental underlying data representation, including #guile and I believe #chez as well. and I think #r6rs record protocols make them both extremely extensible and parametric, as well as #guix's define-record-type* lazy records which serve a similar purpose with a lot less cognitive overhead.

lots of cool record systems out there, I'm interested in understanding the tradeoffs of #gauche's approach in particular, which is to implement records within a #clos-like object system, which seems to allow you to work with generic methods on record-types (which is something that GOOPs is not very good at, for example). what approach did you go with for your record system?

#scheme tip of the day: need to get a quick overview of all the modules, imports and exports in a scheme repository? the #akku package manager can handle this for any #r6rs or #r7rs compatible scheme (which includes #guile): just cd into the repository, and run "akku scan", and it will list all this and more for you.

#lisp #guix

You know #TDD ?! What? I mean #tootDrivenDevelopment ? 🤔🤔

♥️ I need help to figure out what it looks like! ♥️

I start with a simple #scheme #code #snippet and you modify it. The resulting code has to fit in one toot!
If you can't execute the code. It's broken. The last committer should fix it.
So make it portable ! 🚀

(display "hello schemers")

#scheme #schemer #schemers #lisp #lisper
#r5rs #r6rs #r7rs #coding #programming #fun #friday #guile #chezscheme #gauche #racket #chickenscheme #gambit