From: Andy Wingo <wingo@pobox.com>
To: Andreas Rottmann <a.rottmann@gmx.at>
Cc: Guile Developers <guile-devel@gnu.org>
Subject: Re: Quasisyntax broken?
Date: Sun, 26 Jul 2009 18:30:08 +0200 [thread overview]
Message-ID: <m3hbwztnjj.fsf@pobox.com> (raw)
In-Reply-To: <87ljmcsb6r.fsf@delenn.lan> (Andreas Rottmann's message of "Sat, 25 Jul 2009 23:30:04 +0200")
Hi,
On Sat 25 Jul 2009 23:30, Andreas Rottmann <a.rottmann@gmx.at> writes:
> Andy Wingo <wingo@pobox.com> writes:
>
>> On Fri 24 Jul 2009 00:35, Andreas Rottmann <a.rottmann@gmx.at> writes:
>>
>>> Andy Wingo <wingo@pobox.com> writes:
>>>
>>>> On Fri 03 Jul 2009 02:04, Andreas Rottmann <a.rottmann@gmx.at> writes:
>>>>
>>>>> Playing around with Guile's now-in-core syntax-case support (using Git
>>>>> HEAD as of today), I found that quasisyntax seems quite broken:
>>>>
>>>> We've spoken over IRC since then, but for those that do not frequent
>>>> there, it's simply not implemented. You can implement it in terms of
>>>> with-syntax, though. Did you have a patch for that, Andreas?
>>>>
>>> Yep, the patch is attached:
>>
>> What is the license of this code?
>>
> It's under the (unmodified) MIT license, see
> <http://srfi.schemers.org/srfi-process.html>
Hm. I have no idea what this means for Guile. It seems we need either a
disclaimer or an assignment. Now, it seems that something happened in
the past with psyntax which would seem to go against this, though:
commit 9d1a28471c4e69ee151a85d44f8888a69bf102ec
Author: Jim Blandy <jimb@red-bean.com>
Date: Mon Oct 19 13:43:50 1998 +0000
We can't include Kent Dybvig's syntax-case macro expander in the
core Guile distribution, because we don't have copyright
assignments for this code. We can certainly distribute them as a
separate package, but Guile should be FSF code.
* syncase.scm, psyntax.pp, psyntax.ss: Removed.
* Makefile.am (ice9_sources): Removed syncase.scm, psyntax.pp, and
psyntax.ss.
* Makefile.in: Regenerated.
* Makefile.am (ice9_sources): Add getopt-gnu-style.scm.
* Makefile.in: Regenerated.
But then:
commit a63812a2fef2f81b8c4eca04c858e42b62e455f9
Author: Jim Blandy <jimb@red-bean.com>
Date: Mon Oct 19 15:38:05 1998 +0000
Talked to Stallman. Actually, the syntax-case copyright is no
problem. Duh.
* Makefile.am (ice9_sources): Revert last change.
* syncase.scm, psyntax.pp, psyntax.ss: Added again.
* Makefile.in: Regeneretade.
So I don't know what the deal is. I'll defer to Neil and Ludovic.
> it would be (IMHO) kinda dumb to have to ignore/rewrite all the
> perfectly (L)GPL-compatible BSD- and MIT-licensed code that's out
> there, as you cannot expect the respective authors to all sign
> copyright assignments for Guile...
Yes, I agree.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2009-07-26 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 0:04 Quasisyntax broken? Andreas Rottmann
2009-07-23 21:31 ` Andy Wingo
2009-07-23 22:35 ` Andreas Rottmann
2009-07-23 22:48 ` Andy Wingo
2009-07-25 21:30 ` Andreas Rottmann
2009-07-26 13:15 ` Ludovic Courtès
2009-07-26 16:30 ` Andy Wingo [this message]
2009-07-26 22:06 ` Ludovic Courtès
2009-07-27 22:51 ` Neil Jerram
2009-08-20 21:19 ` 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=m3hbwztnjj.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=a.rottmann@gmx.at \
--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).