On 14/03/2008, Kon Lovett <[EMAIL PROTECTED]> wrote:
> Kinda the inverse of '(uses ...)'. For use when compiling files for
> inclusion in a binary library. Extensions have (almost) no need to
> use it.
Yeah, I got piqued by my noobishness, so I went and looked at the
revised chapter 1 in the wik
On Mar 14, 2008, at 12:46 PM, Leonardo Valeri Manera wrote:
On 14/03/2008, Graham Fawcett <[EMAIL PROTECTED]> wrote:
(declare (uses ...)) doesn't do what you think it does. :-) It's for
specifying relationships between compilation units, not modules
(eggs).
I usually do csc -X module1 -R m
On 14/03/2008, Graham Fawcett <[EMAIL PROTECTED]> wrote:
> (declare (uses ...)) doesn't do what you think it does. :-) It's for
> specifying relationships between compilation units, not modules
> (eggs).
>
> I usually do csc -X module1 -R module2 myfile.scm (where module1 is
> needed at compila
(declare (uses ...)) doesn't do what you think it does. :-) It's for
specifying relationships between compilation units, not modules
(eggs).
I usually do csc -X module1 -R module2 myfile.scm (where module1 is
needed at compilation, and module2 is needed at runtime).
Graham
_
The file can be seen here:
http://git.einit.org/?p=einit/modules/scheme.git;a=blob_plain;f=src/chicken-core/core.scm;hb=testing
If I compile it without (declare (uses ...)) everything is fine.
With that line, I get:
csc -O2 -C "" -Isrc/module-scheme-chicken src/chicken-core/core.scm
-o einit-sub
