Summary

The require-library ID & import IMPORT module name forms are disjoint

Metadata

• Id: 25c34aa3e94986ab3b64853a56ea1d22a7d0c699
• Trac id: 320
• Type: enhancement
• Reporter: kon
• Owner:
• Cc:
• Status: closed
• Component: unknown
• Estimated difficulty:
• Resolution: fixed
• Priority: not urgent at all
• Milestone: 4.9.0
• Version: 4.5.x
• Changetime: 2012-09-24 21:47:48 UTC
• Created: 2010-08-09 22:33:50 UTC
• Keywords: syntax module library

Description

The require-library ID allows (srfi #) but the import IMPORT module name does not due to the interpretation of a structured IMPORT as an import specifier only.

Perhaps the module name concept in the context of an 'import' could be extended to allow structured module names where the base name does not clash with the set of import specifier tags. Specifically '(srfi #)'.

So

(import

 ...
 (prefix (only (srfi 1) map for-each member assoc) srfi-1:)
 ...)

(require-library ... (srfi 1) ...)

would be legal.

(The require-library (srfi # ...) & (version ...) forms are not relevant here.)

(The more general case of structured module/library names is not discussed here.)

Changes and comments

[2010-08-13 10:07:37 UTC] felix changed status from new to closed

[2010-08-13 10:07:37 UTC] felix set resolution to fixed

[2010-08-13 10:07:37 UTC] felix wrote:

See "experimental", commit 7f9f454. `require-extension` now also tries to handle this syntax. Note that only a single SRFI-number is currently allowed in the import form.

[2011-06-01 09:00:41 UTC] felix changed milestone from 4.7.0 to 4.8.0

[2011-06-01 09:00:41 UTC] felix wrote:

Milestone 4.7.0 deleted

[2012-09-24 21:47:48 UTC] felix changed milestone from 4.8.0 to 4.9.0

[2012-09-24 21:47:48 UTC] felix wrote:

Milestone 4.8.0 deleted