caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Cc: caml-list@davidb.org, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Announce: Schoca-0.2.3 released
Date: 25 Oct 2004 16:40:44 +1000	[thread overview]
Message-ID: <1098686444.3075.236.camel@pelican.wigram> (raw)
In-Reply-To: <20041025.150855.13740131.garrigue@math.nagoya-u.ac.jp>

On Mon, 2004-10-25 at 16:08, Jacques Garrigue wrote:

> That's why I call it muddy. The FSF (who wrote the GPL) insists that
> dynamic linking creates a derivative work, while in that case the
> linking only occurs at execution. And this makes sense, because
> otherwise the GPL would say nothing more than the LGPL.
> Now, it could be argued that when you load code into the toplevel,
> this is not the toplevel that is using the code (it has no dependency
> on it). But this kind of argument can turn very subjective.

Of course. As can any attempt for law, legislation, or authority
to try to make distinctions between things that no sane programmer
would distinguish.

It's like trying to teach people the difference between a 
compiler, translator and interpreter. In the end the good teacher
knows it's only a vague distinction to help thinking, and the
good student soon learns the teacher was telling a white lie.
They're just all programs.

So too, trying to distinguish 'source code' from 'binary'
and even say specifically what 'linking' means is all 
plainly power politics with no technical merit.

Mathematically, it's all just coding.

-- 
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850, 
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net



-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2004-10-25  6:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-24  9:03 Christoph Bauer
2004-10-24 18:29 ` skaller
2004-10-25  2:58   ` David Brown
2004-10-25  3:38     ` Jacques Garrigue
2004-10-25  5:01       ` David Brown
2004-10-25  6:08         ` Jacques Garrigue
2004-10-25  6:40           ` skaller [this message]
2004-10-25  8:00         ` Ville-Pertti Keinonen
2004-10-25 14:35           ` Stefan Monnier
2004-10-25 15:15             ` [Caml-list] " skaller
2004-10-25 15:25               ` Stefan Monnier
2004-10-25 14:42           ` [Caml-list] " skaller
2004-10-25 15:52           ` David Brown
2004-10-25 18:10           ` Hartmann Schaffer
2004-10-25  5:56       ` [Caml-list] licence stuff again skaller
2004-10-25  5:18     ` [Caml-list] Announce: Schoca-0.2.3 released skaller
2004-10-25  5:29       ` David Brown
2004-10-25  6:07         ` skaller
2004-10-27 14:42           ` Sven Luther
2004-10-27 14:40       ` Sven Luther
2004-10-27 16:04         ` skaller
2004-10-27 17:46         ` David Brown

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1098686444.3075.236.camel@pelican.wigram \
    --to=skaller@users.sourceforge.net \
    --cc=caml-list@davidb.org \
    --cc=caml-list@inria.fr \
    --cc=garrigue@math.nagoya-u.ac.jp \
    /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 NNTP newsgroup(s).