Hi,
I defined a macro. I compiled it separately and built it into my main
program. When my main program calls the load procedure on normal Scheme
source files, the procedures in these files use the macro without
complaint.
However, when it loads the dynamic object code created from
On Wed, Sep 10, 2014 at 12:01:54AM -0700, alex wrote:
Hi,
Hello Alex,
I defined a macro. I compiled it separately and built it into my main
program. When my main program calls the load procedure on normal Scheme
source files, the procedures in these files use the macro without
complaint.
On Wed, 10 Sep 2014 00:01:54 -0700
alex a...@cs.utah.edu wrote:
Hi,
I defined a macro. I compiled it separately and built it into my main
program. When my main program calls the load procedure on normal
Scheme source files, the procedures in these files use the macro
without complaint.
I think you need to define the import library when building both test.scm
and test.import.scm. If I do so, your test works:
dleslie@marvin:~$ csc -s test.scm -j test
dleslie@marvin:~$ csc -s test.import.scm -j test
dleslie@marvin:~$ csi
CHICKEN
(c) 2008-2014, The Chicken Team
(c) 2000-2007,
On Wed, 10 Sep 2014 07:05:43 -0700
Daniel Leslie d...@ironoxide.ca wrote:
I think you need to define the import library when building both
test.scm and test.import.scm. If I do so, your test works:
dleslie@marvin:~$ csc -s test.scm -j test
dleslie@marvin:~$ csc -s test.import.scm -j test
Thank you, everyone, for responding so quickly. You helped me fix my
problems. I'm now passing my source file with my macro definition to the
compiler with the -extend option.
Here was my first problem:
I defined a macro. I compiled it separately and built it into my main
program.
If the
