From: ken.dickey@whidbey.com
To: Maxime Devos <maximedevos@telenet.be>
Cc: guile-user@gnu.org
Subject: Re: Advice on ST-Object data-structure setup
Date: Wed, 17 Apr 2024 11:29:59 -0700 [thread overview]
Message-ID: <accb2788e307da3a034c58df1494761f@whidbey.com> (raw)
In-Reply-To: <20240417183421.CGaK2C00F3BbbgK01GaM5L@laurent.telenet-ops.be>
On 2024-04-17 09:34, Maxime Devos wrote:
> LICENSE says 'Copyright (c) 2016', but some files date from 2024. It's a bit inconsistent ... Do you mean that changes >2016 are public domain, or not covered by BSD license, or the inconsistency is an oversight?
Ah. Thanks.
I used Larceny Scheme for the initial development and am just starting
to update the code to use in Guile. Guile code broken so far.
Just an oversight. Open source license.
-KenD
next prev parent reply other threads:[~2024-04-17 18:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 21:14 Advice on ST-Object data-structure setup ken.dickey
2024-04-17 7:10 ` Basile Starynkevitch
2024-04-17 7:14 ` Basile Starynkevitch
2024-04-17 16:34 ` Maxime Devos
2024-04-17 14:28 ` ken.dickey
2024-04-17 16:34 ` Maxime Devos
2024-04-17 18:29 ` ken.dickey [this message]
2024-04-20 9:49 ` Mikael Djurfeldt
2024-04-20 10:03 ` Mikael Djurfeldt
2024-04-20 15:08 ` ken.dickey
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=accb2788e307da3a034c58df1494761f@whidbey.com \
--to=ken.dickey@whidbey.com \
--cc=guile-user@gnu.org \
--cc=maximedevos@telenet.be \
/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).