From: Mike Gran <spk121@yahoo.com>
To: Guile-devel <guile-devel@gnu.org>
Subject: Guile examples directory and box examples
Date: Sat, 10 Jun 2023 16:22:59 +0000 (UTC) [thread overview]
Message-ID: <1605022274.1340885.1686414179067@mail.yahoo.com> (raw)
In-Reply-To: 1605022274.1340885.1686414179067.ref@mail.yahoo.com
Hello Guile-
It has been a long time since I noticed the existence of the examples
directory in the Guile source. Looking at it, I wonder if it is
worth keeping.
Aside from typo and copyright fixes, it has been unmodified since
the (web http) example from 2011.
The box examples do not really demonstrate current best practice.
Also, I have some doubt that users are looking at that code
for inspiration, rather than what online sources provide.
It uses "make installcheck", which is uncommon.
Regards,
Mike Gran
parent reply other threads:[~2023-06-10 16:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1605022274.1340885.1686414179067.ref@mail.yahoo.com>]
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=1605022274.1340885.1686414179067@mail.yahoo.com \
--to=spk121@yahoo.com \
--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).