public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: mikel evins <mevins@me.com>
To: Per Bothner <per@bothner.com>
Cc: mikel evins <mevins@me.com>, Kawa mailing list <kawa@sourceware.org>
Subject: Re: parameters not working?
Date: Wed, 14 May 2014 02:19:00 -0000	[thread overview]
Message-ID: <4AB83A6F-03EB-4A0F-9A1E-34C02A15FBD4@me.com> (raw)
In-Reply-To: <5A552792-7BD1-4B70-BB06-D6721C6DAC36@me.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

  reply	other threads:[~2014-05-14  2:19 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13  4:09 the right way to compile and load modules mikel evins
2014-05-13  7:29 ` Charles Turner
2014-05-13  7:45   ` mikel evins
2014-05-13  7:49   ` Per Bothner
2014-05-13  7:55 ` Per Bothner
2014-05-13  8:02   ` mikel evins
2014-05-13  8:40     ` mikel evins
2014-05-13 10:23       ` mikel evins
2014-05-14  1:13       ` mikel evins
2014-05-14  1:19         ` parameters not working? mikel evins
2014-05-14  1:31           ` Per Bothner
2014-05-14  1:41             ` mikel evins
2014-05-14  2:12             ` mikel evins
2014-05-14  2:19               ` mikel evins [this message]
2014-05-14  9:32             ` mikel evins
2014-05-14 16:07               ` Per Bothner
2014-05-14  1:43         ` the right way to compile and load modules Per Bothner
2014-05-14  1:50           ` mikel evins
2014-05-14  2:05           ` mikel evins
2014-05-14  3:52             ` Per Bothner
2014-05-14  3:59               ` mikel evins
2014-05-14  6:29                 ` Per Bothner
2014-05-14  6:52                   ` mikel evins
2014-05-14 18:59                     ` Kawa experience [was: the right way to compile and load modules] Per Bothner
2014-05-14 20:06                       ` Charles Turner
2014-05-15  2:16                       ` mikel evins
2014-05-14  7:26                   ` the right way to compile and load modules mikel evins
2014-05-14  7:33               ` Per Bothner
2014-05-14  7:35                 ` mikel evins
2014-05-14 18:46                 ` Per Bothner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AB83A6F-03EB-4A0F-9A1E-34C02A15FBD4@me.com \
    --to=mevins@me.com \
    --cc=kawa@sourceware.org \
    --cc=per@bothner.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).