[armedbear-devel] bug with initialize-instance and keyword arguments
srolls24 at gmail.com
Sat Oct 10 02:40:49 UTC 2009
Erik Huelsmann wrote:
> On Fri, Oct 9, 2009 at 5:18 PM, Steve Rolls <srolls24 at gmail.com> wrote:
>> Ville Voutilainen wrote:
>>> 2009/10/7 Steve Rolls <srolls24 at gmail.com>:
>>>> There is still at least one case that abcl is not happy with. A keyword
>>>> argument with a default value.
>>> This problem is fixed by r12179. Our initarg checking used string= for the
>>> element of the method lambda list, but that element is a list if
>>> there's a default
>>> value for the argument.
>> Thanks again Ville.
>> BTW, the performance improvements in head vs. the last version I used
>> (0.13) are very impressive. Running regression tests on my code (which
>> makes fairly extensive use of CLOS) took 300 seconds with 0.13. Now it
>> is 24 seconds on the first run and 14 seconds on the second run.
> Wow! That's *very* impressive. Do you have time to investigate what
> might be causing this? Could it be that you're not only heavily using
> CLOS extensively, but you're using deep call stacks a lot too? Or
> maybe you're using structures a lot?
> Anyway, if you can share some experience with us what commits made
> your tests faster and which ones slowed it down, that could really be
> helpful information in improving our performance further. (And we're
> definitely dedicated to doing so!)
When I get a chance, I'll try to look into it some more.
More information about the armedbear-devel