William Harold Newman wrote:
>Your goals sound reasonable. I think we mostly agree about goals, and
>disagree about policy because of differences of opinion about the
>actual consequences of policies. Such disagreements are supposed to be
>easier to resolve than disagreements about goals...
Well, given this, there doesn't seem to be much in the way of options.
I am willing to bring my form up to 0.7.3, but there are some caveats.
I am not going to write the code to make the current versions of
sbcl/cmucl bootstrap this, someone who find this a major priority is
welcome to do so.
At some point I will require a feature freeze so that I can synchronise
I will require a sequential list of patches to apply to the source to
bring it up to the normal level, applying a single diff across the whole
system, I suspect will not be workable, but it should be doable to apply
the patches in sequence, and fix them as they break.
I will need the unicode form to be default, and then to later produce
code to make it efficient for the cases where extended character sets
are not utilised. It is not workable to maintain such fundamental
disparities for such minimal returns.
Given this, I will make a minimally different system from what is
presently available which is at the latest version, which will not
include the character databases.
More or less this will be what I have already produced, but with the
character data-base files removed, and the #[!][+-]unicode options
removed to make the unicode form default. If it proves straight-forward,
I will include an option to allow character arrays to use an 8 bit
substrate in this release, otherwise it can be handled later on in a
more general form.
Given this, I expect that it can be completed within a month or so,
although I am somewhat busy lately.
Naturally, this will cause work for other people, but I don't see any
The non-x86 ports will also need to write some vop code, but it should
be fairly straight-forward.