Am Mi., 27. Mai 2020 um 11:41 Uhr schrieb Lassi Kortela <xxxxxx@lassi.io>:

> I agree. However, there shouldn't be a problem with sticking to one
> extension for all kinds of Scheme S-expression files.

Yes, but different kinds of Scheme files (top-level programs, scripts,
library definitions) may have to be treated differently by, say,
implicit make rules. Think of automated tests
(https://www.gnu.org/software/automake/manual/html_node/Parallel-Test-Harness.html#Parallel-Test-Harness),
etc.

More than one file extension is really helpful here. Otherwise, people
will invent their own extensions, making code bases less readable.