[replying to Peter] > I don't grok what you are saying here. Do you want to copy the entire > CHICKEN 4 egg list to CHICKEN 5? It may be better to copy individual > eggs later, when we've finished all our module refactorings. That way, > the eggs won't all break at once, and only the eggs people are really > interested in will survive the transition.
I think as many eggs as possible should make the transition, at least those that are in svn. > Maybe not just for internal use. Perhaps a chicken.string module could > contain these things plus the CHICKEN-specific ones from data-structures, > like string-intersperse and such? these functions are useful to user > code, too. Especially if we optimise them by removing all the silly > polymorphisms from the SRFI-13 implementation. By restricting them to internal use, we can use faster variants, and it will make user-code less confusing if it uses the "official" eggified definitions. Otherwise people will start mixing official and internal SRFI procedures. Isn't one of the goals of CHICKEN-5 to make the API cleaner? felix _______________________________________________ Chicken-hackers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-hackers
