I want to see such test cases to make sure it can't be fixed and is indeed broken. Is it surprising I want to know, why do you want to (or rather forcefully did) deprecate widely adopted and documented interface relevant for at least three maintained Common Lisp implementations? The only thing I've heard so far, that something will /break/ under conditions I don't know. You know ASDF, so it should be easy for you to convince me with an example.
That would convince me that something isn't right with the interface and they ought to be marked as deprecated (i.e in ECL documentation) if fix is impossible. Otherwise, as already stated, seems like an arbitrary decision.
Also, if ASDF has such cases in the regression tests (i.e marked as expected fail), then there will be no doubt that something ought to be done with it. Right now we have a very emotional comment, that the interface "must die" in the code, what isn't very convincing.
I want to see such test cases to make sure it can't be fixed and is indeed broken. Is it surprising I want to know, why do you want to (or rather forcefully did) deprecate widely adopted and documented interface relevant for at least three maintained Common Lisp implementations? The only thing I've heard so far, that something will /break/ under conditions I don't know. You know ASDF, so it should be easy for you to convince me with an example.
That would convince me that something isn't right with the interface and they ought to be marked as deprecated (i.e in ECL documentation) if fix is impossible. Otherwise, as already stated, seems like an arbitrary decision.
Also, if ASDF has such cases in the regression tests (i.e marked as expected fail), then there will be no doubt that something ought to be done with it. Right now we have a very emotional comment, that the interface "must die" in the code, what isn't very convincing.