Hi Daphne, Thank you for your talk transcript!
Daphne Preston-Kendal <[email protected]> writes: > Even Guile has this problem, because it’s still culturally normal > among users of that implementation to use its own define-module > declaration instead of the standard R6RS or R7RS library or > define-library Would it be possible to have a utility that transforms these files to standard scheme? A code walker written in r7rs that runs on every scheme implementation and can output a standard r7rs version? Something like standardize --from guile /path/to/source -o /path/to/target Or bail out and noting the unresolvable deviations from r7rs (and maybe even suggest changes to make it work on r7rs). To make sure it works this would have to run on the source scheme. > shy of compromise; the uncompromising pursuit of perfection, even > though perfection is a quality nobody will ever agree on, may be why > we have struggled so much to move onwards while other languages have > not. On the other hand, there is a lot that Scheme reports got right. The past seven years working professionally with Java and (later) Javascript I repeatedly hit on problems that wouldn’t have existed with Scheme. So I think that pursuit of perfection has merit. On yet another hand: the writers of the reports got things right I would have gotten wrong. So I don’t know how much impact my experience should have. How were Scheme reports able to get so many things right? Best wishes, Arne -- Unpolitisch sein heißt politisch sein, ohne es zu merken. draketo.de
signature.asc
Description: PGP signature
