unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Dmitry Bogatov <KAction@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Implement doctest utility as guild script
Date: Sun, 29 Sep 2013 21:07:18 +0400	[thread overview]
Message-ID: <87li2fd0ah.fsf@gnu.org> (raw)
In-Reply-To: <871u47kdgn.fsf@gnu.org>

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


Ludovic Courtès <ludo@gnu.org> writes:

> I share Ian Price’s concerns regarding the fundamental idea behind
> doctest.  Namely, writing code in strings means that syntax errors can
> only be detected very late, and that the code in there cannot easily
> refer to anything outside;
What do you mean outside? I think it encourages pure function.

Am I understand right, that you would like to check such tests on
`make all`, and not on `make check`?

> furthermore, that pollutes docstrings, whose
> goal is to provide a help string for users.
Definitely right. At current state. But it is possible to separate
actual english documentation string and doctests. Displaying them
in (help function-name) may be turned off or, imho (since I like examples
in documentation), better, made optional.

--
Best regards, Dmitry Bogatov <KAction@gnu.org>,
Free Software supporter and netiquette guardian.
	git clone git://kaction.name/rc-files.git --depth 1
	GPG: 54B7F00D
Html mail and proprietary format attachments are forwarded to /dev/null.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2013-09-29 17:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-28  4:49 [PATCH] Implement doctest utility as guild script KAction
2013-09-29 12:40 ` Ludovic Courtès
2013-09-29 17:07   ` Dmitry Bogatov [this message]
2013-09-29 19:14     ` Ludovic Courtès

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=87li2fd0ah.fsf@gnu.org \
    --to=kaction@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).