From: tomas@tuxteam.de
To: guile-user@gnu.org
Subject: [SOLVED] Trying to get friends with SRFI-19
Date: Wed, 22 Jul 2020 23:20:39 +0200 [thread overview]
Message-ID: <20200722212039.GB19139@tuxteam.de> (raw)
In-Reply-To: <20200720212703.GC31180@tuxteam.de>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
On Mon, Jul 20, 2020 at 11:27:03PM +0200, tomas@tuxteam.de wrote:
> Hi,
>
> I'm trying to parse some stuff, part of which are date
> strings of the form "20200106", i.e. "YYYYMMDD" [...]
> Is there a canonical way to validate a date string?
I ended up rolling my own (and converting to SRFI-19 date
once validation says "OK").
Is there interest in such a thing? i.e.
valid-date? (y m d) -> bool
returns whether (y m d) is a valid Gregorian date.
I wouldn't mind putting it up somewhere, with a suitable
license. OTOH, it's a whopping 36 lines or so, so perhaps
not worth it ;-D
Cheers
-- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2020-07-22 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 21:27 Trying to get friends with SRFI-19 tomas
2020-07-22 21:20 ` tomas [this message]
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=20200722212039.GB19139@tuxteam.de \
--to=tomas@tuxteam.de \
--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).