[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-janitors] #703: Restructure core libraries
From: |
Chicken Trac |
Subject: |
Re: [Chicken-janitors] #703: Restructure core libraries |
Date: |
Mon, 21 May 2012 20:15:38 -0000 |
#703: Restructure core libraries
-----------------------------+----------------------------------------------
Reporter: felix | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: core libraries | Version: 4.7.x
Resolution: | Keywords:
-----------------------------+----------------------------------------------
Comment(by alaric):
Names like 'extras' and 'utils' are certainly meaningless. It would be
nice and clean if we could just filter them out into suitably-
meaningfully-named libraries and just keep the generic names as re-
exporting compatibility modules.
Slightly trickier is if we want to move anything out of existing well-
named modules such as 'ports', as then we can't have backwards
compatability without choosing a new name for the new module that doesn't
export the names in question.
Personally, I'd like more finer-grained modules, avoiding generic terms
such as "extras" as they just end up as grab-bags full of things, and
looking for a function involves searching the list of modules for a
specific module and then searching "extras" if you can't find it. In other
words, I propose that the rule used to decide what granularity to use
should be to put oneself in the shoes of somebody looking for any of the
functions in a module, and seeing if all of those functions would seem to
be implied by its name, without it misleadingly suggesting any functions
that are elsewhere.
--
Ticket URL: <http://bugs.call-cc.org/ticket/703#comment:1>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Chicken-janitors] #703: Restructure core libraries,
Chicken Trac <=