From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27164 invoked by alias); 25 Aug 2013 22:26:36 -0000 Mailing-List: contact cgen-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cgen-owner@sourceware.org Received: (qmail 27150 invoked by uid 89); 25 Aug 2013 22:26:36 -0000 X-Spam-SWARE-Status: No, score=1.0 required=5.0 tests=AWL,BAYES_20,KHOP_DYNAMIC2,RDNS_DYNAMIC autolearn=no version=3.3.2 Received: from 173-13-178-50-sfba.hfc.comcastbusiness.net (HELO seba.sebabeach.org) (173.13.178.50) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with (AES256-SHA encrypted) ESMTPS; Sun, 25 Aug 2013 22:26:35 +0000 Received: from seba.sebabeach.org (localhost [127.0.0.1]) by seba.sebabeach.org (8.14.7/8.14.7) with ESMTP id r7PMQJc5010016 for ; Sun, 25 Aug 2013 15:26:19 -0700 Received: (from dje@localhost) by seba.sebabeach.org (8.14.7/8.14.7/Submit) id r7PMQItE010015; Sun, 25 Aug 2013 15:26:18 -0700 From: Doug Evans To: cgen@sourceware.org Subject: guile 2.0? Date: Sun, 25 Aug 2013 22:26:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-q3/txt/msg00002.txt.bz2 Now that Guile 2.0 has been out for awhile, anyone mind if we update cgen to require it? There are some non-upward-compatible changes I'm seeing in 2.0.9, and I'm not sure we need to support 1.6 or 1.8 any longer. I can also imagine taking advantage of some newer features, but at least for a first step I'd like to get cgen usable with the latest Guile. [Whether to stick with R*RS or use some Guile-specific features is a good question, I'm leaning towards R*RS though I always imagined replacing cos.scm with something like goops.]