Nathan Froyd <froydnj@...> writes:
> On Tue, Sep 29, 2009 at 4:34 AM, Christophe Rhodes <csr21@...> wrote:
>> Is there a good way that I can publish my work in progress so that the
>> wisdom of the Internet can perform the merge (given that I have so few
>> spare cycles to do SBCL development at the moment)?
> I'd suggest creating a repo for yourself on repo.or.cz (or your
> favorite DVCS hosting site du jour) and stuffing it there. If it's
> ready for public consumption, I can do the merge and commit for you;
> otherwise I can do the merge and put it someplace useful.
I've now rebased my work against CVS HEAD, I think. It's viewable at
the git repository at <http://rvw.doc.gold.ac.uk/sullivan/git/sbcl.git>
should have its server-info sufficiently updated for pulls to work.
Since I have your attention, can I draw your attention to commit
65367ef26f08132ea6d8e2eb4c3ebbca0ca21bd2, and in particular the diff
around WRAP-EXTERNAL-FORMAT-FUNCTIONS; I've taken your nice
external-format structure with its sane protections, removed all those
protections, and fiddled about with the insides. Would there be a
better way? (In particular, I lose the interned nature of external
formats by doing this).
The next step in my path is to teach each external format about a
sensible default replacement character, and then to make the streams
opened for the terminal (and stdin/stdout/stderr) to use a
replacing external-format rather than a harsh one, so that you don't get
into the state of wedging your system because there's something on some
stream that is illegal for the external format. The octets code will
need to be taught about this :replacement external-format too.