From: nalaginrut <nalaginrut@gmail.com>
To: Tomas By <tomas@basun.net>
Cc: guile-user@gnu.org
Subject: Re: "unbound variable"
Date: Mon, 27 Jun 2011 17:18:53 +0800 [thread overview]
Message-ID: <1309166333.3070.80.camel@Renee-desktop> (raw)
In-Reply-To: <11ad4ae2bf30b0902bad2e5e002fdf16.squirrel@webmail.xs4all.nl>
> Hi again,
>
> Thanks for the help so far.
>
> On Mon, June 27, 2011 10:38, nalaginrut wrote:
> > I can't give accurate answer because you provided less information. So I
> > just give a guess:
> > If you have wrapped a module in mapdisplay.scm, you'd have imported some
> > symbols out of this module. I know you can see get-map in REPL's
> > "current-module", but mapdisplay can't see it in it's own
> > "current-module". They are different.
> > If you write this get-map within a module, you may use "#:use-module" in
> > mapdisplay.scm. If not, you need to import it from your .so file with
> > FFI such as "dynamic-link". You may checkout it out in the manual.
>
> Well, as I tried to explain, "get-map" is statically linked into the
> executable, defined with "scm_c_define_gsubr" which is called from the
> "inner_main" that is passed to "scm_boot_guile".
>
> I don't think I should have to also dynamically link it.
>
> Do I need to do another "define_gsubr" (or whatever) from inside mapdisplay?
>
> /Tomas
>
Well, I see your situation. And I must say that I don't blend the
extension with executive entry file. So I'm not sure whether a symbol
imported in inner_main directly would be available in every module.
--
GNU Powered it
GPL Protected it
GOD Blessed it
HFG - NalaGinrut
--hacker key--
v4sw7CUSMhw6ln6pr8OSFck4ma9u8MLSOFw3WDXGm7g/l8Li6e7t4TNGSb8AGORTDLMen6g6RASZOGCHPa28s1MIr4p-x hackerkey.com
---end key---
next prev parent reply other threads:[~2011-06-27 9:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 8:00 "unbound variable" Tomas By
2011-06-27 3:40 ` nalaginrut
2011-06-27 8:12 ` Tomas By
2011-06-27 8:38 ` nalaginrut
2011-06-27 8:56 ` Tomas By
2011-06-27 9:18 ` nalaginrut [this message]
2011-06-27 9:41 ` Peter Brett
2011-06-27 21:44 ` Linas Vepstas
2011-06-28 6:15 ` Tomas By
2012-01-08 17:04 ` Andy Wingo
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1309166333.3070.80.camel@Renee-desktop \
--to=nalaginrut@gmail.com \
--cc=guile-user@gnu.org \
--cc=tomas@basun.net \
/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).