From: Alex Shinn <foof@synthcode.com>
Subject: Re: srfi-26
Date: Mon, 19 Jan 2004 17:22:19 +0900 [thread overview]
Message-ID: <87zncktkjo.wl@strelka.synthcode.com> (raw)
In-Reply-To: <rmiptdju3lo.fsf@fnord.ir.bbn.com>
At 16 Jan 2004 13:53:55 -0500, Greg Troxel wrote:
>
> Or if the author's employer claims that something was a work for
> hire. That's the point of the employer-disclaimer, which is separate
> conceptutally from the copyright assignment. So for PD code this
> still applies; it's arguably only really PD if the person who said so
> was the copyright owner, so a signed statement from the author that
> it's PD and from employer (anyone who might have a work-for-hire
> claim) disclaiming copyright interest should do, at least
> conceptually.
I guess that makes sense, though it's really inconvenient for something
like the Scheme community which shares code so freely.
But how about the 14-line, not-significant-for-copyright version? There
are only so many ways to implement cut without artificially using a
round-about technique... if you won't take that code, I'll write a
program to automatically generate every possible cut and post it to the
list, forever banning Guile from using SRFI-26! :P
--
Alex
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-01-19 8:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 2:17 srfi-26 Alex Shinn
2004-01-15 9:36 ` srfi-26 Daniel Skarda
2004-01-21 0:44 ` srfi-26 Marius Vollmer
2004-01-23 0:44 ` srfi-26 Kevin Ryde
2004-01-24 10:22 ` srfi-26 Daniel Skarda
2004-02-28 20:15 ` srfi-26 Kevin Ryde
2004-02-29 10:04 ` srfi-26 Daniel Skarda
2004-03-01 21:10 ` srfi-26 Kevin Ryde
2004-01-15 22:08 ` srfi-26 Kevin Ryde
2004-01-16 3:28 ` srfi-26 Alex Shinn
2004-01-16 4:13 ` srfi-26 Paul Jarc
2004-01-16 18:53 ` srfi-26 Greg Troxel
2004-01-19 8:22 ` Alex Shinn [this message]
2004-01-19 16:43 ` srfi-26 Stephen Compall
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=87zncktkjo.wl@strelka.synthcode.com \
--to=foof@synthcode.com \
/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).