<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#000000" text="#FFFFFF">
<br>
Good suggestions, thanks. I strongly agree about the doc. There
are various other featurey things on my list too.<br>
<br>
About utilities and macros: don't know if you looked closely, but
they are not just copies of what was in quux in those files in the
tarball -- I tried to hand pick only what was needed. In
hand-picking I sometimes (undisciplinedly) picked stuff as a larger
group, with some of the group not actually needed, but that went
together with what was needed. So it's more of a mess, but maybe
more to the point that you might imagine :/ I think we can sort
that out when more is added to qitab, but until then I'm not super
motivated about it right now. As I clean up more of quepasa that
will probably change.<br>
<br>
On 01/20/2014 10:05 PM, Faré wrote:
<blockquote
cite="mid:CAN7nBXcN3Q7p1tbWVRcm_03tNkqP=gbQiKO6yPhsXxtkYQ38gQ@mail.gmail.com"
type="cite">
<pre wrap="">Dear Derek,
congratulations for releasing Quepasa!
<a class="moz-txt-link-freetext" href="https://github.com/qitab/qitab/">https://github.com/qitab/qitab/</a>
Some remarks:
* macros and utilities probably have to be moved out of quepasa into
the rest of qitab, and split into units that make more sense. Maybe
you should extract those specific macros that you're using and define
just these, in their own file. Maybe you should be using utilities in
alexandria and/or poiu where they exist, instead of incompatible the
quux variants, where applicable. We should avoid multiplying entities,
this way. For the sake of compatibility, we could define a
backward-compatibility package where quux primitives are defined in
terms of more standard things, where they exist. You don't need to do
all that; still, if you can identify which subset of quux macros and
utilities you're using, it's a good idea to define a new library that
provides just that, and put it in many files under, say,
qitab/utility/
* I see you're not using the newfangled package-system thingie. You
don't have to; nevertheless, if you start using it, you may grow to
liking it.
* When you have time, the most urgent is probably more documentation.
* You may want to create a page on cliki.net, maybe on cl-user.net,
and maybe announce on comp.lang.lisp or some blog or public feed.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• <a class="moz-txt-link-freetext" href="http://fare.tunes.org">http://fare.tunes.org</a>
Lubarsky's Law of Cybernetic Entomology:
There's always one more bug.
</pre>
</blockquote>
<br>
</body>
</html>