From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay1-d.mail.gandi.net (relay1-d.mail.gandi.net [217.70.183.193]) by sourceware.org (Postfix) with ESMTPS id 3DB8C3858018 for ; Sat, 6 Feb 2021 12:48:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 3DB8C3858018 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=lassi.io Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=lassi@lassi.io X-Originating-IP: 82.181.134.218 Received: from sunshower.local (82-181-134-218.bb.dnainternet.fi [82.181.134.218]) (Authenticated sender: lassi@lassi.io) by relay1-d.mail.gandi.net (Postfix) with ESMTPSA id A009C240003; Sat, 6 Feb 2021 12:48:02 +0000 (UTC) Subject: Re: SRFI inclusion To: Helmut Eller , kawa@sourceware.org References: <97fcf177-4168-b564-9ce3-32396986d5a1@bothner.com> From: Lassi Kortela Message-ID: <7e94903d-63bc-bb61-4c7e-9c02537f77f3@lassi.io> Date: Sat, 6 Feb 2021 14:48:01 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: kawa@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Kawa mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Feb 2021 12:48:08 -0000 > A common interface would be nice, but designing good interfaces is not > easy. If somebody comes up with a good interface later, maybe it can be > added post-hoc; not ideal, but should be doable with a layer of > indirection. > > What bothers me more, is that maintaining those libraries separately for > each Scheme system doesn't scale. It would probably be better to do it > like they do it for the BOOST libraries. Have one common code base that > can be compiled with different compilers; possibly with implementation > specific versions but maintained as part of the common code base by the > people who use and care about the libraries. I agree that the maintenance burden for practical Scheme libraries is growing too great for any one person or implementation. We've just been having discussions in this general direction on the #scheme IRC channel. Several people would like something like the SRFI process, but allowing for API evolution, with less stringent requirements to get the API design right all at once.