On Tue, Dec 21, 2004 at 10:45:51AM +, Henning Makholm wrote:
> Scripsit Josh Triplett <[EMAIL PROTECTED]>
>
> > One suggestion: you might be able to make the necessary modifications to
> > BSD yacc, which I think descends from the original UNIX yacc by way of
> > BSD UNIX and the whole AT&T vs
Scripsit Andrew Suffield <[EMAIL PROTECTED]>
> On Tue, Dec 21, 2004 at 10:45:51AM +, Henning Makholm wrote
>> In this particular case, the modifications consist of changing the
>> output language from C to something else. That sounds fairly major;
>> the entire parsing engine would have been h
On Tue, Dec 21, 2004 at 10:45:51AM +, Henning Makholm wrote:
> Scripsit Josh Triplett <[EMAIL PROTECTED]>
>
> > One suggestion: you might be able to make the necessary modifications to
> > BSD yacc, which I think descends from the original UNIX yacc by way of
> > BSD UNIX and the whole AT&T vs
Scripsit Josh Triplett <[EMAIL PROTECTED]>
> One suggestion: you might be able to make the necessary modifications to
> BSD yacc, which I think descends from the original UNIX yacc by way of
> BSD UNIX and the whole AT&T vs. BSD issue.
In this particular case, the modifications consist of changin
Justin Pryzby wrote:
> On Sun, Dec 19, 2004 at 08:59:06PM -0800, Josh Triplett wrote:
>>Justin Pryzby wrote:
>>>What kind of license is associated with code produced by Yacc?
>>Presuming this modified yacc isn't trivially replaceable with a Free
>>yacc, this would prevent these packages from being
On Sun, Dec 19, 2004 at 08:59:06PM -0800, Josh Triplett wrote:
> Justin Pryzby wrote:
> > What kind of license is associated with code produced by Yacc?
>
> Presuming this modified yacc isn't trivially replaceable with a Free
> yacc, this would prevent these packages from being uploadable to main.
Justin Pryzby wrote:
> What kind of license is associated with code produced by Yacc?
Well, code produced by yacc is derivative both of the yacc input file
and the yacc parser being used.
> Upstream IRAF apparently has a "UNIX source license" and uses a
> modified yacc to produce two of the files
On Sun, Dec 19, 2004 at 11:29:47PM +0100, Måns Rullgård wrote:
> And this is probably the reason we have thousands of (probably
> invalid) software patents instead.
Copyright law is only a minor part of that issue.
--
Raul
Raul Miller <[EMAIL PROTECTED]> writes:
> On Sun, Dec 19, 2004 at 03:45:40PM -0500, Justin Pryzby wrote:
>> This is probably hotly debated, but how do math-algorthm copyrights
>> work?
>
> Articles about mathematics, and specific expressions of algorithms,
> are copyrightable, but the concepts are
On Sun, Dec 19, 2004 at 03:45:40PM -0500, Justin Pryzby wrote:
> This is probably hotly debated, but how do math-algorthm copyrights
> work?
Articles about mathematics, and specific expressions of algorithms,
are copyrightable, but the concepts aren't.
In the U.S. 17 USC 102 states:
In no cas
This is probably hotly debated, but how do math-algorthm copyrights
work?
There are lots of these:
==> ./iraf/math/llsq/original_f/qrbd.f <==
c subroutine qrbd (ipass,q,e,nn,v,mdv,nrv,c,mdc,ncc)
c c.l.lawson and r.j.hanson, jet propulsion laboratory, 1973 jun 12
c to appear in 'solvin
By the way,
I'm not subscribed, please Cc: me.
What kind of license is associated with code produced by Yacc?
Upstream IRAF apparently has a "UNIX source license" and uses a
modified yacc to produce two of the files. The source includes a
README:
This directory contains the source for t
Hello,
As you may recall, I am (unofficially) maintaining the IRAF data
analysis package. IRAF includes NCAR from UCAR (.. Atmospheric
Research). It was previously decided [1] that the license from NCAR
was very much not DFSG-free.
However, the NCAR routines are now available under the GPL. I
13 matches
Mail list logo
