Attila Lendvai
writes:
>> We can provide new, improved functionality without breaking anything.
>> And keep old systems working forever with new ASDF.
>
>
> "forever" is a very strong word Anton. e.g. if CL doesn't fade into
> the category of history in 10 years, meaning that a significant number
On Fri, Mar 28, 2014 at 10:12 AM, Zach Beane wrote:
> Faré writes:
>
>> In the end it's a matter of WHO specifies the settings for some
>> compilation: the system author or the user.
>
> Or, in this case, Faré.
>
Once it's accepted that ASDF will enforce the file type decided by the
author, ASDF
On Fri, Mar 28, 2014 at 11:33 AM, Zach Beane wrote:
> Faré writes:
>
>> On Fri, Mar 28, 2014 at 11:00 AM, Zach Beane wrote:
>>> Faré writes:
>>>
Once it's accepted that ASDF will enforce the syntax variables decided
>>>
>>> This seems more like an "if" than a "once" to me.
>>>
>> Then plea
On Fri, Mar 28, 2014 at 6:19 AM, Zach Beane wrote:
> Faré writes:
>
>> It's not a matter of lint at all.
>
> Very true. Lint is an *optional* program, and you can easily choose to
> ignore it.
>
The analogy with lint is totally bogus here. The case that was vaguely
analogous to lint indeed was th
> "Fare" == Far writes:
Fare> Thanks a lot, Anton!
Fare> Well, here's a valid argument in favor of 'single-float as the
Fare> default: making 'double-float the default breaks 22 systems in
Fare> Quicklisp (a bit fewer when you consider that some systems only
Fare> depende
Faré writes:
> On Fri, Mar 28, 2014 at 11:00 AM, Zach Beane wrote:
>> Faré writes:
>>
>>> Once it's accepted that ASDF will enforce the syntax variables decided
>>
>> This seems more like an "if" than a "once" to me.
>>
> Then please argue that. I for one fully agree that the big question is
>
On Fri, Mar 28, 2014 at 11:00 AM, Zach Beane wrote:
> Faré writes:
>
>> Once it's accepted that ASDF will enforce the syntax variables decided
>
> This seems more like an "if" than a "once" to me.
>
Then please argue that. I for one fully agree that the big question is
not about the specific defa
Faré writes:
> Once it's accepted that ASDF will enforce the syntax variables decided
This seems more like an "if" than a "once" to me.
Zach
Faré writes:
> In the end it's a matter of WHO specifies the settings for some
> compilation: the system author or the user.
Or, in this case, Faré.
Zach
Faré writes:
> It's not a matter of lint at all.
Very true. Lint is an *optional* program, and you can easily choose to
ignore it.
Zach
> Fare> Yes I do, although I just committed a change to override
> Fare> *read-default-float-format* to 'double-float, which I believe is
> more
> Fare> useful.
>
> I disagree that that is more useful. While I almost always use
> doubles, there are lots of reasons to use singles. Just
> "Fare" == Far writes:
Fare> On Thu, Mar 27, 2014 at 2:00 PM, Anton Vodonosov
wrote:
>> Fare, if femlisp configures *read-default-float-format*
>> why does it fail with your ASDF change? Do you restore standard
>> CL syntax around every file compilation?
Fare> Yes I do
12 matches
Mail list logo
