unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guile-user@gnu.org
Subject: Re: timestamp
Date: Sat, 12 Feb 2022 19:32:26 +0200	[thread overview]
Message-ID: <8335kornx1.fsf@gnu.org> (raw)
In-Reply-To: <87zgmwry5u.fsf@elephly.net> (message from Ricardo Wurmus on Sat,  12 Feb 2022 14:49:20 +0100)

> From: Ricardo Wurmus <rekado@elephly.net>
> Date: Sat, 12 Feb 2022 14:49:20 +0100
> Cc: guile-user@gnu.org
> 
> > The argument of lack of examples in the Guile/Guix documentation has
> > been made several times now, or at least, I've seen it being made
> > several times
> 
> The Guix documentation contains examples, but it’s already very long and
> intimidating, so we started the Cookbook for more extensive tutorials
> and examples.
> 
> It hasn’t seen as much uptake by contributors as I hoped, but it’s there
> and can be extended with more examples, big and small.

I don't think just adding examples will cut it, although it will
certainly help.

My take of the issue is that the Guile reference manual is little more
than the collection of the doc strings of the various Guile APIs.  The
doc strings are by their very nature quite terse and lack the "glue":
the text which will explain the relative merits and demerits of each
API wrt the other, the factors to consider when deciding which APIs to
use, etc.  It also doesn't make it easy to have helpful
cross-references.  Moreover, adding examples to the doc strings will
have a disadvantage: it will increase the memory footprint of running
Guile applications.

Which is why I think the effort should be in the direction of
extending the parts of the manual that aren't produced from the doc
strings, but instead are written by humans to help other humans.



  parent reply	other threads:[~2022-02-12 17:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-12  8:37 timestamp adriano
2022-02-12  8:52 ` timestamp Vivien
2022-02-12  9:43   ` timestamp adriano
2022-02-12 11:49     ` timestamp Ricardo Wurmus
2022-02-12 12:32       ` timestamp tomas
2022-02-12 12:38       ` timestamp Eli Zaretskii
2022-02-12 13:30       ` timestamp adriano
2022-02-12 13:42         ` timestamp adriano
2022-02-12 13:49         ` timestamp Ricardo Wurmus
2022-02-12 13:55           ` timestamp adriano
2022-02-12 14:01             ` Guile cookbook ? adriano
2022-02-12 14:15               ` Ricardo Wurmus
2022-02-12 15:01                 ` adriano
2022-02-12 15:30               ` Olivier Dion via General Guile related discussions
2022-02-12 17:11               ` Zelphir Kaltstahl
2022-02-12 17:32           ` Eli Zaretskii [this message]
2022-02-12 17:48             ` Examples in Guile documentation Zelphir Kaltstahl
2022-02-12  9:01 ` timestamp tomas
2022-02-12  9:49   ` timestamp adriano
2022-02-12 12:50   ` timestamp Eli Zaretskii
2022-02-12 13:01     ` timestamp tomas
2022-02-12 15:23     ` timestamp adriano

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=8335kornx1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=rekado@elephly.net \
    /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).