From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: guile-devel@gnu.org
Subject: Re: Adding the doctests module to guile-lib or guile?
Date: Thu, 17 Oct 2024 08:56:11 +0200 [thread overview]
Message-ID: <87plnzusj8.fsf@web.de> (raw)
In-Reply-To: <87v8445bt8.fsf@web.de> (Arne Babenhauserheide's message of "Fri, 26 Apr 2024 18:27:31 +0200")
[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]
Hi,
did this question drown in other messages? Should this go
- to guile-lib
- to guile
- elsewhere?
My preference would be guile, because then it would be available for
everyone learning Guile Scheme and I could more easily use it in
tutorials
Best wishes,
Arne.
"Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
> Hi,
>
> I’ve been using my doctests implementation for years now, and it works
> beautifully for me, so I would like to contribute it — either to
> guile-lib as (tests doctest) or to guile (maybe (ice-9 doctest)?).
>
> Working code is here:
> https://hg.sr.ht/~arnebab/wisp/browse/examples/doctests.scm?rev=tip
>
>
> Example usage:
> ;; https://hg.sr.ht/~arnebab/wisp/browse/examples/doctests-test.scm?rev=tip
> (define-module (examples doctests-test))
>
> (import (examples doctests))
>
> (define (foo)
> #((tests
> ('foo
> (test-equal "bar" (foo)))))
> "bar")
>
> (define %this-module (current-module))
> (define (main args)
> " Testing doctests"
> #((tests ('mytest
> (test-assert #t)
> (test-assert #f))))
> (doctests-testmod %this-module))
>
>
> How should I go forward to contribute it (and should I)?
>
>
> Best wishes,
> Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2024-10-17 6:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 16:27 Adding the doctests module to guile-lib or guile? Dr. Arne Babenhauserheide
2024-10-17 6:56 ` Dr. Arne Babenhauserheide [this message]
2024-11-23 23:02 ` Dr. Arne Babenhauserheide
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=87plnzusj8.fsf@web.de \
--to=arne_bab@web.de \
--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).