This is the mail archive of the
kawa@sourceware.org
mailing list for the Kawa project.
Re: Unknown feature name 'srfi-26'
- From: Per Bothner <per at bothner dot com>
- To: Charles Turner <chturne at gmail dot com>
- Cc: Alcides Flores Pineda <alcides dot fp at gmail dot com>, Kawa mailing list <kawa at sourceware dot org>
- Date: Mon, 08 Jul 2013 16:09:49 -0700
- Subject: Re: Unknown feature name 'srfi-26'
- References: <87pputu7lv dot fsf at inspiron-640m dot AFP-HOME> <CAPMhJv0jKX_pzdfYXrxSepD=CwvZfWwb1oy+0Z7Hw-rhJWgzLQ at mail dot gmail dot com>
On 07/08/2013 05:08 AM, Charles Turner wrote:
CUT and CUTE and actually builtins (Per, why is that, and not part of
a library instead?)
Some srfi are builtins. srfi-26 probably shouldn't be, in retrospect,
but it probably isn't worth changing.
I can't see any removal of srfi-26 mappings from
the ChangeLogs, so I'm bemused as to how that once worked.
I'm not sure either. I vaguely remember coming across
some similar (or the same) issue not that long ago, but I don't
remember anything concrete.
Needless to
say, you can safely remove the line containing (require 'srfi-26) and
expect to be able to still use the CUT and CUTE forms.
I guess we could make (require 'srfi-26) be a no-op, the
way (import :26 cut) is. That would be reasonable transition
we if might at some point make srfi-26 non-builtin.
--
--Per Bothner
per@bothner.com http://per.bothner.com/