|
errno groveler in C
Lassi Kortela
(27 Jun 2020 12:03 UTC)
|
|
Re: errno groveler in C
John Cowan
(27 Jun 2020 12:10 UTC)
|
|
Re: errno groveler in C
Lassi Kortela
(27 Jun 2020 12:16 UTC)
|
|
Re: errno groveler in C
hga@xxxxxx
(27 Jun 2020 12:26 UTC)
|
|
SRFI directory layout
Lassi Kortela
(27 Jun 2020 12:40 UTC)
|
|
Re: SRFI directory layout hga@xxxxxx (27 Jun 2020 13:42 UTC)
|
|
Re: SRFI directory layout
Arthur A. Gleckler
(27 Jun 2020 20:07 UTC)
|
|
Re: SRFI directory layout
John Cowan
(27 Jun 2020 13:53 UTC)
|
|
Re: SRFI directory layout
Arthur A. Gleckler
(27 Jun 2020 20:01 UTC)
|
|
Re: errno groveler in C
Arthur A. Gleckler
(27 Jun 2020 16:35 UTC)
|
|
Re: errno groveler in C
hga@xxxxxx
(27 Jun 2020 12:21 UTC)
|
|
Re: errno groveler in C
Lassi Kortela
(27 Jun 2020 12:34 UTC)
|
|
Re: errno groveler in C
Lassi Kortela
(27 Jun 2020 13:51 UTC)
|
|
Re: errno groveler in C
hga@xxxxxx
(27 Jun 2020 14:24 UTC)
|
|
Re: errno groveler in C
Lassi Kortela
(27 Jun 2020 14:32 UTC)
|
> From: Lassi Kortela <xxxxxx@lassi.io> > Date: Saturday, June 27, 2020 7:40 AM > >> My suggestions are that all implementation materials be under the srfi >> directory, that way the top directory is less cluttered, and my MANIFEST >> file at that level can capture them all. Each implementation or tool >> should then be under its own subdirectory, like "chibi-scheme" for mine. > > Arthur should chime in as the SRFI editor and suggest a standardized > layout for SRFI repos :) As it stands, the improvised layouts make them > hard to navigate unless one is already familiar with a particular repo. Good points. Thinking some more, I would add to my suggestions using a more descriptive name than "srfi" for the directory to stash implementations in. While I'm at it, Arthur, is my impression correctly that while a SRFI's text gets frozen after finalization, this is not true of the accompanying materials like implementations? - Harold
