If I hg pull and hg update using my checkout of https://bitbucket.org/S11001001/weblocks-dev I can't see that change in.
Also, it looks like you're going through a horrible bogus and roundabout way to have weblocks-prevalence depend on weblocks-memory without doing it directly. Can you delete this prepare-prevalence-op nonsense, and replace it with (1) adding weblocks-memory to :depends-on (2) calling any necessary initialization function at the correct moment (whether it be compile-time, load-time, runtime or coffee-time). On Sunday, January 27, 2013 10:58:22 AM UTC+1, o_z wrote: > > Thank you, patch applied, compatibility with latest asdf (2.26.152) is > fixed. As for other questions I don't know yet. > > понедельник, 31 декабря 2012 г., 0:31:55 UTC+2 пользователь > [email protected] написал: >> >> Dear weblocks hackers, >> >> recent failures of ASDF 2.26.36 to compile weblocks led me to give a look >> at your .asd files. >> >> In the end, I improved backwards compatibility, and I believe that the >> latest ASDF (currenty 2.26.45) will compile weblocks. Please test, though. >> >> However, while I was at it, I made those small improvements to your .asd >> files. >> >> Also, I don't quite understand what is the intent of the >> prepare-prevalence-op thingie. How is it not but a horribly inefficient way >> to do the same as including :weblocks-memory in your :depends-on? >> >> I would also cut on all the defpackage overhead when all you're doing is >> using a single defsystem form. ASDF will load your systems in a package >> where defsystem already works, for lambda's sake! >> >> -- You received this message because you are subscribed to the Google Groups "weblocks" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/weblocks?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
