With the release of scsh 0.6.3, the 0.6 series of scsh has become
feature-complete: everything that ever worked in scsh 0.5 should work
in scsh 0.6. We'll continue work on the 0.6 series, but we'll focus
on fixing bugs there and perhaps bringing in non-intrusive features.
The 0.6.4 release cycle will probably commence in a few days.
After 0.6.4, we intend to focus our active development on a complete
overhaul of scsh, cleaning up its API and improving its
maintainability. Here are some of the things we have in store
- Scsh will be properly modularized instead of mostly everything being
stuck in one giant structure.
- The shell subsystem will become compositional and take a more
combinator-style form. This means that process forms and extended
process forms will merge. We'll remove allusions to an interactive
shell syntax; this is the wrong layer to implement them.
- We'll standardize the code base on SRFI 9 for records and use more
transparent names for the record procedures.
- We'll make scsh internally independent from the port revelation
machinery, moving towards removing port revelation altogether.
- We'll make scsh a better Unix citizen: it will build outside the
source tree, and we'll move to a more GNU-style layout for the
- We'll make the networking code IPv6-ready, abstracting out things
like IP addresses.
- We'll reduce the actual changes to the Scheme 48 code base, getting
closer to the point where we can distribute scsh separately.
Generally, as we make API changes, we'll provide compatibility
structures with as close as possible to the 0.6 API as possible. The
goal for the new API is to incorporate as many of the lessons in
learned in close to 10 years of scsh usage at once so we can go on
Comments and suggestions are welcome, as always.
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla