From: Zelphir Kaltstahl <zelphirkaltstahl@gmail.com>
To: guile-user@gnu.org
Subject: Re: R7RS On Guile
Date: Wed, 24 Apr 2019 21:48:40 +0200 [thread overview]
Message-ID: <aad4a951-f0fa-c6c5-c38d-942e1ee06c6d@gmail.com> (raw)
In-Reply-To: <mailman.127.1556121627.20760.guile-user@gnu.org>
Hi Amirouche!
I just looked at the source hut thingy. I do not really understand where
to go from there.
I see the to-do list: https://todo.sr.ht/~amz3/guile-r7rs
On each item there is already a name before the chat icon in the table.
But I guess that is only the creator of the to-do list item (you?)?
I click on an item, lets say "(scheme repl)". Then I get to this page:
https://todo.sr.ht/~amz3/guile-r7rs/41
There I see a link to a PDF and a GitLab project
https://gitlab.com/akkuscm/akku-r7rs/ .
However, the linked project seems to not be specific to any to-do list
item. No matter what item I check, it always leads me to this akku
thingy. Does that mean, that it is already implemented somewhere in the
akku? Should it not be marked as closed on the to-do list then?
And how does that source hut thing work? Do I create a new repository on
GitLab and simply start implementing things according to what the PDF
defines as the standard? I would like to see example code for other
things R7RS to see if I can understand anything and see, if I feel
capable of contributing anything of value, or if it is above my level.
Sorry for all the questions! I have not used source hut before.
Regards,
Zelphir
On 4/24/19 6:00 PM, guile-user-request@gnu.org wrote:
> Message: 1
> Date: Tue, 23 Apr 2019 21:22:45 +0200
> From: amirouche@hyper.dev
> To: guile-user gnu <guile-user@gnu.org>
> Subject: R7RS On Guile
> Message-ID: <31b28dccf5cf612aa6134ad20001097b@hyper.dev>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>
> Hello,
>
>
> If you like R7RS and also like Guile you might join me
> in getting together R7RS libraries as Guile libraries.
>
> I am just getting started not much is done as of yet.
> The repository is over the rainbow at source hut:
>
> https://git.sr.ht/~amz3/guile-r7rs
>
> There is continuous integration that is setup.
> Documentation is written in markdown and the project
> rely on Guile srfi-64 testing framework.
>
> My plan is to focus on (scheme base) to get tests
> and documentation up.
>
> Feel free to reach me if you would like to join the fun.
>
>
> Happy hacking!
next parent reply other threads:[~2019-04-24 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.127.1556121627.20760.guile-user@gnu.org>
2019-04-24 19:48 ` Zelphir Kaltstahl [this message]
2019-04-24 21:24 ` R7RS On Guile Amirouche Boubekki
2019-04-23 19:22 amirouche
2019-04-23 19:55 ` Brett Gilio
2019-04-23 20:34 ` amirouche
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=aad4a951-f0fa-c6c5-c38d-942e1ee06c6d@gmail.com \
--to=zelphirkaltstahl@gmail.com \
--cc=guile-user@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).