get procedure?

2010-02-17 Thread Paul Emsley
I don't understand what xxx is. Can you help? (Bit of a noob question, I feel). SCM rest = SCM_EOL; SCM arg_list = SCM_EOL; arg_list = scm_cons(SCM_MAKINUM(4), arg_list); arg_list = scm_cons(SCM_MAKINUM(1), arg_list); SCM func = xxx("-"); SCM v = scm_apply_1(func, arg_list, rest

loading a module

2010-02-17 Thread Tomas By
Hello one more time, There was a little problem in mytest.c, where I had declared a pointer only and no address location. This was the cause of the segmentation fault. With the following source files, the code Linas posted, after some modifications, is compiled to a binary `vepstas' which runs fi

Re: get procedure?

2010-02-17 Thread Paul Emsley
Paul Emsley wrote: I don't understand what xxx is. Can you help? (Bit of a noob question, I feel). SCM rest = SCM_EOL; SCM arg_list = SCM_EOL; arg_list = scm_cons(SCM_MAKINUM(4), arg_list); arg_list = scm_cons(SCM_MAKINUM(1), arg_list); SCM func = xxx("-"); SCM v = scm_appl

Re: get procedure?

2010-02-17 Thread Thomas Thiriez
Hi Paul, Here is what you should use for xxx: SCM FindFunc(const char *funcName) { SCM funcSymbol = scm_c_lookup(funcName); if (!funcSymbol) // undefined symbol return 0; return scm_variable_ref(funcSymbol); } Regards, Thomas On Feb 17, 2010, at 7:25 PM, Paul Emsley wrote

Re: get procedure?

2010-02-17 Thread dsmich
Thomas Thiriez wrote: > Hi Paul, > > Here is what you should use for xxx: > > SCM FindFunc(const char *funcName) > { >SCM funcSymbol = scm_c_lookup(funcName); > >if (!funcSymbol) > // undefined symbol > return 0; > >return scm_variable_ref(funcSymbol); > } Oi!

Re: get procedure?

2010-02-17 Thread Andy Wingo
Hi, On Wed 17 Feb 2010 20:03, Thomas Thiriez writes: > Here is what you should use for xxx: Hm, not quite :) > SCM FindFunc(const char *funcName) > { >SCM funcSymbol = scm_c_lookup(funcName); scm_c_lookup gives you a variable object, as you note below; better to call it `funcVar' (or `fun

Re: loading a module

2010-02-17 Thread Andy Wingo
On Wed 17 Feb 2010 19:26, "Tomas By" writes: > I think the "file not found" message is just the general dynamic-link- > anything error. Yes, it is a libltdl bug. See http://lists.gnu.org/archive/html/libtool/2009-12/msg00057.html More than that, it's tough to say; I'm mercury-ignorant. A -- h

Re: loading a module

2010-02-17 Thread Tomas By
On Wed, February 17, 2010 21:12, Andy Wingo wrote: > On Wed 17 Feb 2010 19:26, "Tomas By" writes: > More than that, it's tough to say; I'm mercury-ignorant. Well, since the `vepstas' binary works, the Mercury bit seems ok. Do you have any suggestions for how to debug it? Is there anything I can

Re: loading a module

2010-02-17 Thread Thien-Thi Nguyen
() "Tomas By" () Wed, 17 Feb 2010 21:21:43 +0100 ldd doesn't seem to report anything wrong, but is there any other test available from the shell? If you have strace(1), you can use the script (i call it ~/bin/st): #!/bin/sh exec strace -f -e open "$@" 2>&1 | grep -v o.such.file to find