From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: guile-unify -> guile-log
Date: Wed, 21 Mar 2012 22:58:15 +0100 [thread overview]
Message-ID: <CAGua6m0rUv7WiOMy0FNg6RO5uh-FGaFEph0sintf4G5CQDkLZQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
Hi,
If you wondered about the results of my endavour with logic programming for
guile I
finally made a repo that is self containd and does not mode guile (HORROR
STORIES HERE)
Anyway here is the link for the repo at gitorius,
https://gitorious.org/gule-log/guile-log
I just added a small repo with type-checking code that uses guile-log, see
https://gitorious.org/typed-guile/typed-guile
-------------------
The astute reader will see that documentation is lacking and probably when
I stabilized guile-contracts
I wiill start documenting the these codes.
Regards
Stefan
[-- Attachment #2: Type: text/html, Size: 755 bytes --]
next reply other threads:[~2012-03-21 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 21:58 Stefan Israelsson Tampe [this message]
2012-03-21 22:01 ` guile-unify -> guile-log Noah Lavine
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=CAGua6m0rUv7WiOMy0FNg6RO5uh-FGaFEph0sintf4G5CQDkLZQ@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).