replacing fare-matcher with optima, and some asd cleanups

48 views
Skip to first unread message

tu...@google.com

unread,
Dec 30, 2012, 5:31:55 PM12/30/12
to webl...@googlegroups.com
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!

f.diff

tu...@google.com

unread,
Jan 25, 2013, 8:33:54 AM1/25/13
to webl...@googlegroups.com, tu...@google.com
Weblocks maintainers, please apply the patch, and consider the below suggestions.

Re-posting with a more painfully obvious subject line considering the lack of replies.
f.diff

o_z

unread,
Jan 26, 2013, 3:04:28 AM1/26/13
to webl...@googlegroups.com, tu...@google.com
What environment you use for asdf ? I've upgraded quicklisp to latest version and all is ok (I use sbcl and suppose you too).

понедельник, 31 декабря 2012 г., 0:31:55 UTC+2 пользователь tu...@google.com написал:

Faré TUNES

unread,
Jan 26, 2013, 10:42:08 AM1/26/13
to o_z, webl...@googlegroups.com
On Sat, Jan 26, 2013 at 3:04 AM, o_z <olex...@gmail.com> wrote:
> What environment you use for asdf ? I've upgraded quicklisp to latest
> version and all is ok (I use sbcl and suppose you too).
>
I'm using the latest ASDF from git, currently 2.26.146.
http://common-lisp.net/gitweb?p=projects/asdf/asdf.git

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
The smallest minority on earth is the individual. Those who deny individual
rights, cannot claim to be defenders of minorities. — Ayn Rand

Pixie

unread,
Jan 26, 2013, 10:51:12 AM1/26/13
to public-weblocks-/JY...@plane.gmane.org



The OP is Fare, the current ASDF maintainer and creator of fare-matcher,
and is talking about an updated version of ASDF not yet in Quicklisp
which he has been working on.



On 2013.01.26 02:04, o_z wrote:
> What environment you use for asdf ? I've upgraded quicklisp to latest
> version and all is ok (I use sbcl and suppose you too).
>
> О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫, 31 О©╫О©╫О©╫О©╫О©╫О©╫О©╫ 2012 О©╫., 0:31:55 UTC+2 О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫
> tu...-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org О©╫О©╫О©╫О©╫О©╫О©╫О©╫:

o_z

unread,
Jan 27, 2013, 4:58:22 AM1/27/13
to webl...@googlegroups.com, tu...@google.com
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 пользователь tu...@google.com написал:
Dear weblocks hackers,

tu...@google.com

unread,
Feb 18, 2013, 9:29:50 AM2/18/13
to webl...@googlegroups.com, tu...@google.com
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).

o_z

unread,
Feb 18, 2013, 12:15:42 PM2/18/13
to webl...@googlegroups.com, tu...@google.com


On Monday, February 18, 2013 4:29:50 PM UTC+2, tu...@google.com wrote:
If I hg pull and hg update using my checkout of https://bitbucket.org/S11001001/weblocks-dev I can't see that change in.
This repository is outdated. Links on site will be updated soon. Relevant one is https://github.com/skypher/weblocks

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).
Ok, this has to be solved, problem was already discussed but it needed to dive in it for solving. You've provided useful information. 
Thank you for reporting, I've created issue https://github.com/skypher/weblocks/issues/27 and will fix it soon.

o_z

unread,
Apr 28, 2013, 10:56:13 PM4/28/13
to webl...@googlegroups.com, tu...@google.com


понедельник, 18 февраля 2013 г., 19:15:42 UTC+2 пользователь o_z написал:


On Monday, February 18, 2013 4:29:50 PM UTC+2, tu...@google.com wrote:
If I hg pull and hg update using my checkout of https://bitbucket.org/S11001001/weblocks-dev I can't see that change in.
This repository is outdated. Links on site will be updated soon. Relevant one is https://github.com/skypher/weblocks

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).
Ok, this has to be solved, problem was already discussed but it needed to dive in it for solving. You've provided useful information. 
Thank you for reporting, I've created issue https://github.com/skypher/weblocks/issues/27 and will fix it soon.
Fixed issue 
Reply all
Reply to author
Forward
0 new messages