On 29 July 2013 10:21, 白い熊 wrote:
> Hello:
>
> I'm developping a program which I'd like to be able to use without
> modification with Guile as the interpreter as well as Emacs lisp and clisp.
>
>
Cond-expand macro was supposed to assist "conditional compilation",
see an example below. I am not su
Hi, Roland,
What exactly goes wrong when you build your module?
Did you accidentally the error message?
I use this convenience command to augment the linker and compiler flags:
LIBS += $(shell guile-config link)
INCDIRS += $(shell guile-config compile)
Alexei
>> The reason is accessing macros from languages
>> other than C is cumbersome.
>
> Apologies for ignoring you.
Hi, Wingo, Hi, All,
No need to apologise, given your track record I trust you spending
every minute of your time for a good purpose. :)
Lack of time is a good evolutionary filter agains
On 14 November 2012 14:43, Hans Aberg wrote:
> On 14 Nov 2012, at 11:31, Alexei Matveev wrote:
>
>> I see interface of scm_apply_1() and scm_apply() are the same
>> and dont get the difference [1].
>
> File libguile/eval.c in the distribution gives:
> /* Apply a func
On 7 November 2012 03:49, Keith Wright wrote:
>
>
> > (define y (with-output-to-string (lambda()(system "date"
> Tue Nov 6 21:42:41 EST 2012
> > y
> $2 = ""
>
> The stdout of the system call does not go into the string,
> why not?
>
For the same reason you cannot capture stdout of, sa
Quote from
http://lists.gnu.org/archive/html/guile-devel/2001-06/msg00348.html
>> Do we want scm_list_0 to scm_list_9 anyway?
>
> I'd say, forget about scm_list_0. With respect to the others, we should
> at least provide those which are used in libguile (egoistic point of
> view, isn't it?). Ab
[resend to guile-user, first copy went to bug-guile]
Hi, All,
For use from a Fortran program I am collecting API fixes for libguile.so
as wrapper functions for what is provided to C-programs as macros.
I noted that some of the macros are function-macros some are symbol
macros. An example of the l
