Matt Van Gundy wrote:
Thomas,
Thank you, I think that yours is a sane interpretation of that clause. On
further thought, I'd have to concur that, re-implementation of a standard
most likely doesn't imply creation... and the previous licenses seem to
agree.
Thanks for helping me see it
Thomas,
Thank you, I think that yours is a sane interpretation of that clause. On
further thought, I'd have to concur that, re-implementation of a standard
most likely doesn't imply creation... and the previous licenses seem to
agree.
Thanks for helping me see it another way,
Matt
Thomas
I read your paste as being unable to create _new_ classes not published in
the Java Platform Interface JPI.
Referencing the 1.4.2 version; this simply seems like a shorter version
saying the same things, except where the 1.4.2 version said you were
allowed to invent new APIs, but had to publish
Classpath developers,
In an attempt to upgrade my the JVM on my development box to Sun's latest
release I was perusing the new version of the BCL and noticed that the
Java Technology Restrictions section had changed from previous BCLs.
I quote it for reference:
D. Java Technology
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Matt,
have you seen this:
http://developer.classpath.org/mediation/ClasspathFirstSteps#head-9d8423acc71a1bd7817642969981efd5331078d0
Is that answering your question?
cu
Robert
Matt Van Gundy wrote:
Classpath developers,
In an attempt to
Thanks for the pointer Robert,
It is a similar issue, however, the information you linked to didn't quite
answer the question. Because, my question concerns Sun's BCL rather than
the SCSL, there is not issue of being tainted by having seen non-free
source code. I'm bothered by an item in the
6 matches
Mail list logo
