From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Inclusion of guile-log
Date: Tue, 27 Mar 2012 00:02:06 +0200 [thread overview]
Message-ID: <CAGua6m33gByX_tHX5ozs=VLYyEuGD5tR5D6HjXEmDxa8f66xtw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
Hello,
I have now prepared guile-log in such a state that it is usable. The last
item I would like
to close is to document it and put it in relation with kanren.
The software is pretty guile centric and the question is if we would like
to bundle it with guile.
There are always things to improve. And the next pressing thing would be
adjustable stacks
and better thread integration. I would rather have people testing the
current code base before entering new code.
If we feel stongly that guile-log should be able to be used by many threads
at the same time
I would postpone the inclusion. Else I think it is time to consider it.
What do you think?
Regards
Stefan
[-- Attachment #2: Type: text/html, Size: 725 bytes --]
next reply other threads:[~2012-03-26 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 22:02 Stefan Israelsson Tampe [this message]
2012-03-27 7:07 ` Inclusion of guile-log Thien-Thi Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGua6m33gByX_tHX5ozs=VLYyEuGD5tR5D6HjXEmDxa8f66xtw@mail.gmail.com' \
--to=stefan.itampe@gmail.com \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).