This is the mail archive of the
kawa@sourceware.org
mailing list for the Kawa project.
Re: parameters not working?
- From: mikel evins <mevins at me dot com>
- To: Per Bothner <per at bothner dot com>
- Cc: mikel evins <mevins at me dot com>, Kawa mailing list <kawa at sourceware dot org>
- Date: Wed, 14 May 2014 04:32:00 -0500
- Subject: Re: parameters not working?
- Authentication-results: sourceware.org; auth=none
- References: <9F312D97-98C6-4F47-BDD9-B6CAF3868A28 at me dot com> <5371CFD0 dot 7070708 at bothner dot com> <7D1A5D60-5997-4B7A-9176-8F6FA315F016 at me dot com> <ED4375FE-30EE-4ABC-A9DC-2C6C4D67A87A at me dot com> <54132084-D633-4AAA-B2A4-9008FF37F779 at me dot com> <407A6350-04B0-4EC7-A13C-5C1E02D3A482 at me dot com> <5372C761 dot 3050101 at bothner dot com>
On May 13, 2014, at 8:31 PM, Per Bothner <per@bothner.com> wrote:
>
>
> On 05/13/2014 06:19 PM, mikel evins wrote:
>> My next issue: parameters appear to work fine in interactive sessions from loaded files, but not in required or compiled files.
....
> No, that is supposed to work - and seems to do so:
Yep; it works. I discovered my mistake. The failing parameter definition was in a file named client.scm that had a define-simple-class for a class named <client>. Turns out that's a bad idea. Changing the name of the class fixed the problem.