Re: CLX and common-lisp.net

Mikel Bancroft <[email protected]> writes:

>> Well, I'd have thought the first step would be to make your patches
>> public: in the darcs model of distribution, I think that's done by
>> setting up a publically-accessible darcs repository (with "darcs push"
>> to your webspace).  Then those patches can be pulled by both your
>> users (or beta testers) and those making releases.
>
> This is finally done. I've set up a repository from which you can pull
> my changes at
>
>   http://opensource.franz.com/clx/
>
> I redid the work I did previously so that all the allegrocl specific
> code is in dep-allegro.lisp rather than further mangling dependent.lisp
> (which is full of relatively ancient excl code), and updated
> clx.asd. Small changes to the reader conditionalization in depdefs.lisp
> and demos/clx-demos.lisp.

Thank you!  I've finally got round to pulling your changes, looking at
them, and then pushing them up to <http://common-lisp.net/~crhodes/clx>.

Your log message says "Add support for modern Allegro CL."  You might
be aware that there is an unfortunate specialized meaning of "modern"
in the context of Allegro CL which might be colliding with this use:
do you mean modern-as-in-not-ancient or
modern-as-in-lowercase-cl-symbols?  (If the code supports ACL modern
mode but not ANSI mode, that should probably be mentioned in the
release notes...)

Cheers,

Christophe

_______________________________________________
Portable-clx mailing list
[email protected]
http://lists.metacircles.com/cgi-bin/mailman/listinfo/portable-clx
See http://www.cliki.net/clx for darcs URL(s)