[asdf-devel] Last call before code freeze

[Robert P. Goldman]

Sorry. I seem to have been unclear. I was not arguing for holding up  
the release for the optimal solution to this problem.

I was just arguing that we should withhold the partial solution  
(system-depends) so that people don't get wedded to it, in case it's  
not the Right Thing.

We could withhold support for the new feature simply by not parsing  
those arguments, and leave in support so that we could experiment in v  
2.1+.

This will be my last word on the subject. I've laid out reasons why I  
believe it would be better to postpone judgment on this past 2.0  
release. But this is Fare's call, not mine, and I respect his judgment

Best,
R

On Apr 29, 2010, at 23:06, Daniel Herring <dherring at tentpost.com> wrote:

> On Thu, 29 Apr 2010, Robert Goldman wrote:
>
>> That suggests that the current approach, which is:
>>
>> read it all once
>> process the system-depends-on
>> process the other initargs
>>
>> won't get at the root of the system dependency problem. What we need
>> instead is something like
>>
>> slurp it without reading
>> process the system-depends-on
>> /then/ expose it to the reader (if we so choose).
>>
>> I'd like to give this some thought before we lock ourselves into the
>> first approach with as yet unconsidered problems of backward
>> compatibility moving to the second.
>
> That change looks complicated.  I would not recommend delaying the  
> release
> for it to be made.
>
> Unless you think a lot of projects will jump on this broken feature, I
> don't see an issue with backward compatibility in the future.  Hence  
> my
> belief that proper documentation and maybe a style-warning should be
> sufficient.
>
> Later,
> Daniel
>
> _______________________________________________
> asdf-devel mailing list
> asdf-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel