Ricardo Wurmus <[email protected]> skribis: > Ludovic Courtès <[email protected]> writes: > >>> From 1900f3015162cc777ee79883a0cae2a21216d99c Mon Sep 17 00:00:00 2001 >>> From: Ricardo Wurmus <[email protected]> >>> Date: Fri, 6 Nov 2015 22:37:40 +0100 >>> Subject: [PATCH 2/2] gnu: Add microscheme. >>> >>> * gnu/packages/avr.scm (microscheme): New variable. >> >> [...] >> >>> + (home-page "http://microscheme.org/";) >>> + (synopsis "Scheme subset for Atmel microcontrollers") >> >> “Small Scheme implementation targeting microcontrollers”? (“Scheme >> subset” is vague; “Scheme” alone is already quite vague. ;-)) >> >> I would tend to put it in scheme.scm. Also, it apparently builds on all >> the CPUs that we use, so I’m not sure if it’s worth mentioning Atmel >> here? > > I placed it in ‘scheme.scm’ before, but then noticed that we have an > AVR-specific module and moved it there. It’s not a general purpose > implementation of Scheme. > > Microscheme invokes avr-gcc and needs avrdude to upload the binary to > the target. While it can be used on any of the CPUs for which we offer > support, its purpose is to generate binary code for a subset of the > Atmel AVRs: Atmega168/328, Atmega2560, Atmega32u4. > > You can run programmes written in microscheme on something that’s not a > microcontroller by loading up ‘emulator.scm’ first, but that’s just > intended as a development tool.
Ah OK, then indeed, avr.scm is a good choice. > I don’t mind changing the synopsis, though, as the description is pretty > clear on what targets are supported. OK! Thanks, Ludo’.
