Summary

clarify use if import libraries when compiling modules

Metadata

• Id: efb969c6e176bbbeadf6d212dcb75c02a70f69d5
• Trac id: 292
• Type: defect
• Reporter: felix
• Owner:
• Cc:
• Status: closed
• Component: documentation
• Estimated difficulty:
• Resolution: fixed
• Priority: minor
• Milestone:
• Version: 4.5.x
• Changetime: 2011-04-04 08:31:00 UTC
• Created: 2010-07-21 15:22:31 UTC
• Keywords: documentation modules

Description

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)

Changes and comments

[2010-07-28 12:26:28 UTC] felix changed status from new to closed

[2010-07-28 12:26:28 UTC] felix set resolution to fixed

[2010-07-28 12:26:28 UTC] felix wrote:

Extended faq and Modules pages in the manual somewhat. Not perfectly clear, but hopefully slightly improved (experimental branch).

[2011-04-04 08:31:00 UTC] felix removed milestone 4.6.0

[2011-04-04 08:31:00 UTC] felix wrote:

Milestone 4.6.0 deleted