unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Arne Babenhauserheide <arne_bab@web.de>
To: Chaos Eternal <eternalchaos@shlug.org>
Cc: guile-user@gnu.org
Subject: Re: Python-style doctests in Guile (implemented, please comment)
Date: Mon, 31 Jul 2017 19:44:35 +0200	[thread overview]
Message-ID: <87zibklcs7.fsf@web.de> (raw)
In-Reply-To: <CAGyY8NsT_39B1fRCiUHLHdkxQL+CZfNHC=mVBBj9q87eFkM97g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 684 bytes --]


Chaos Eternal <eternalchaos@shlug.org> writes:

> Great job!
>
> I have a new idea using s-exps to define tests:
> simple way:
> (define-syntax define-examples
> (syntax-rules () ((_ e ...) (quote (e ...)))))
>
> then we can simply (read the-file)  then (match e ((define-examples e ...))
> (do-test e))

So you’d write something like the following?

(define (foo)
        (define-examples
            ((foo) 'foo))
        'foo)

It has the same limitations as I see for define-with-tests (see my other
answer), do you see advantages over the define-with-tests approach?

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-07-31 17:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-30 18:54 Python-style doctests in Guile (implemented, please comment) Arne Babenhauserheide
2017-07-31  8:22 ` Chaos Eternal
2017-07-31 17:44   ` Arne Babenhauserheide [this message]
2017-08-01  1:36     ` Chaos Eternal
2017-07-31 12:51 ` Mark H Weaver
2017-07-31 13:04   ` Panicz Maciej Godek
2017-07-31 17:23   ` Arne Babenhauserheide
2017-08-01 22:04     ` Vítor De Araújo
2017-10-10 18:21       ` Arne Babenhauserheide
2017-10-10 22:40         ` Vítor De Araújo
2017-10-14 13:05           ` 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=87zibklcs7.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=eternalchaos@shlug.org \
    --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).