On Wed, 25 Jun 2014 05:28:39 +0800, Alan Manuel Gloria <almkg...@gmail.com> wrote: > (cond ... else) doesn't work in Guile 1.6 (it's why I coded them as > (cond .. #t) in the first place).
Drat. As noted in the ChangeLog, (cond... #t) causes warnings in chicken Scheme. Hmm. We already do some text processing of kernel.scm in the final build. Perhaps we could detect if (cond ... else) is rejected in configure, and if it is, then substitute the relevant "(else ..." into "(#t ...". Does replacing all "(else " with "(#t " in kernel.scm work in guile 1.6? That would also affect some cond-expand and case statements, as well as cond statements. If we have to only substitute some & not others, we could insert some comments to enable or inhibit text substitution. That might be the simplest solution. That way most people just see "standard modern Scheme" while users of the old guile version 1.6 get working code. --- David A. Wheeler ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Readable-discuss mailing list Readable-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/readable-discuss
