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: Tue, 13 May 2014 21:18:36 -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> <5A552792-7BD1-4B70-BB06-D6721C6DAC36 at me dot com>
On May 13, 2014, at 9:12 PM, mikel evins <mevins@me.com> wrote:
>
> On May 13, 2014, at 8:31 PM, Per Bothner <per@bothner.com> wrote:
>
>> Could you write a simple test-program that shows the problem?
>> Note it should be complete and self-contained, and we need to
>> see the command-line(s) you use to compile and run it.
>
> The simple test case I contrived worked, which suggests I need to look more closely at the context there the parameters are defined in the bigger files where it doesn't work.
So presumably some of the code I'm requiring for the app is somehow breaking parameters. I'll have to search more, but clearly the onus is on me; thanks for your help so far.
A simple test in which I define a parameter in one nearly-empty source file and reference it from another works fine.
The context where it's not working is that I'm defining a couple of parameters at the top of a source file after requiring 20 other modules. In that case, a reference to either of the parameters I defined yields #!null.
I'll have to do a binary search of the requires and see where parameters go south.
Thanks again for the help.
--me