Dear François-René,

On Wed, Sep 23, 2015 at 1:21 AM, Faré <fahree@gmail.com> wrote:

Dear Daniel, dear Jean-Claude,

when asdf-ecl was initially written, its load-fasl-op was intended
as the default way to load a system. Because of implementation bugs
revealed as ASDF improved its testing, this feature was disabled at
some point while developing ASDF 3.1. Now that these implementation
bugs seem to have been solved, for both ECL and MKCL, the question is:
do you guys want me to make load-bundle-op (as it is now named)
the default *load-system-operation* on ECL and/or MKCL?

I have been away from ASDF related concerns long enough for me

to be unable to form a precise understanding of what such move would

precisely mean right now, sorry. But I will try to push out the door

MKCL 1.1.10, the latest maintenance release of the MKCL 1.1.X line,

before the end of this month. And as part of that operation I want

to upgrade the bundled ASDF to 3.1.5. So I'll have then a great
opportunity to get reacquainted with all those load-XXX-op questions,

and I should be able to have an informed opinion by then.

And if so, what test shall I use or not use in determining whether
the implementation is recent enough to use this feature without bug?
I suppose it's better to check against a recent version of ECL that I can test
against this feature than over an older version that may or may not work.

Are we talking about something like #'cl:lisp-implementation-version and

related facilities? If so then you could be interested in:

#'si:mkcl-major-version

#'si:mkcl-minor-version

#'si:mkcl-patch-level

that are available since MKCL 1.1.0. They are meant to make this

kind of assertion return T:

(typep (read-from-string (si:mkcl-minor-version)) 'integer)

Cheers,

JCB