From: Nikolaos Chatzikonstantinou <nchatz314@gmail.com>
To: guile-user@gnu.org
Subject: Re: Help with modules and unit tests
Date: Fri, 8 Dec 2023 03:57:30 -0500 [thread overview]
Message-ID: <CAAQmekc9hHzPSFBY+LuypR=ZGQ7kdTSku3tAPYgWs57Ag3-8NQ@mail.gmail.com> (raw)
In-Reply-To: <CAAQmekf2jxroicFuLSDVxE7PCSn-VnEEXkS-15LZq=tEz1tHiw@mail.gmail.com>
On Fri, Dec 8, 2023 at 1:59 AM Nikolaos Chatzikonstantinou
<nchatz314@gmail.com> wrote:
>
> Hello guile-user list,
>
> I am trying to figure out modules and unit tests on Guile.
Although I still appreciate the responses I may get, to save you all
some keystrokes, I found guile-dns to be a decent (and small) project
that shows off all the relevant bits I was curious about.
<https://git.lysator.liu.se/hugo/guile-dns>. However, I am still
wondering, how is documentation extracted from the source code with
guild doc-snarf?
Regards,
Nikolaos Chatzikonstantinou
next prev parent reply other threads:[~2023-12-08 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 6:59 Help with modules and unit tests Nikolaos Chatzikonstantinou
2023-12-08 8:57 ` Nikolaos Chatzikonstantinou [this message]
2023-12-08 14:26 ` Luis Felipe
2023-12-08 14:29 ` Luis Felipe
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='CAAQmekc9hHzPSFBY+LuypR=ZGQ7kdTSku3tAPYgWs57Ag3-8NQ@mail.gmail.com' \
--to=nchatz314@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).