[armedbear-devel] encoding issues with ABCL

[Faré]

Excellent. Is there a simple way to test the version from within ABCL?
Is the primary value of (lisp-implementation-version) always going to follow
the ASDF convention of having only digits and dots?

Also, I didn't see anything in your patch regarding COMPILE-FILE;
was it already good to go with respect to external formats?

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
If it's not worth doing right, it's not worth doing. — Scott McKay


On Tue, Feb 26, 2013 at 9:56 AM, Mark Evenson <evenson at panix.com> wrote:
> On 2/26/13 0825 , Mark Evenson wrote:
>>
>> On 2/25/13 10:28 PM, Faré wrote:
>>>
>>> Dear ABCL developers,
>>>
>>> it looks like ABCL is not doing the Right Thing with respect to
>>> LOAD's :EXTERNAL-FORMAT argument, instead reading everything with
>>> some dubious default from the environment. Can you fix it?
>
>
> […]
>
>> [#303]: http://trac.common-lisp.net/armedbear/ticket/303
>>
>
> With [r14402][], the version of  asdf-encodings.script from asdf-2.30 with
> the #+abcl conditional commented out now passes.
>
> [r14402]: http://trac.common-lisp.net/armedbear/changeset/14402
>
>
> --
> "A screaming comes across the sky.  It has happened before, but there
> is nothing to compare to it now."