[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-janitors] #292: clarify use if import libraries when compiling
From: |
Chicken Trac |
Subject: |
[Chicken-janitors] #292: clarify use if import libraries when compiling modules |
Date: |
Wed, 21 Jul 2010 13:22:31 -0000 |
#292: clarify use if import libraries when compiling modules
-----------------------------------+----------------------------------------
Reporter: felix | Owner:
Type: defect | Status: new
Priority: minor | Milestone: 4.6.0
Component: documentation | Version: 4.5.x
Keywords: documentation modules |
-----------------------------------+----------------------------------------
Martin DeMello suggested:
{{{
> To compile "test.scm", the compiler needs something to figure out
> what "(import foo)" means. This ting is called the "import library"
> and is produced by passing "-j <modulename>" or "-J" when compiling
> the module:
>
> csc -sJ outer.scm
>
> I'll check whether that can be documented in a clearer manner.
Thanks! Some places it could be documented:
1. expand faq section 8.5 ("Can I load compiled code at runtime?")
2. have another section just after
http://chicken.wiki.br/man/4/Modules%20and%20macros#examples-of-using-
modules
3. the definition of an import library
(http://chicken.wiki.br/man/4/Modules%20and%20macros) makes it sound
like an optional tool that enables more esoteric use cases (even now
that you've explained what it is for, i still can't get that out of
the manual)
}}}
--
Ticket URL: <http://www.irp.oist.jp/trac/chicken/ticket/292>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.
- [Chicken-janitors] #292: clarify use if import libraries when compiling modules,
Chicken Trac <=