Stuart Ballard <[EMAIL PROTECTED]> writes:
> And what about methods? This seems to say that we can't have any
> private methods that Sun don't specify, too...
Don't you love lawyers?
Its quite obvious that there needs to be some non-public classes for
things like returning Enumerations (since the specs are written for
java 1.0.2). Go ahead and make non-public classes in the java.*
namespace.
> Trying to prevent the standard from fragmenting and keep
> implementations up to date with the latest version is a laudable
> aim, even if the techniques used are flawed.
Ummm, but we're not "Java" remember? We can never ever call ourselves
a Java core classes implementation. We should be compatible with
Sun's implementation, but if we weren't, why should Sun be allowed to
control us? We're just implementing an API, and since we've signed no
license with Sun, they should have no rights over us.
If API's can be copyrighted they do have rights over how we use their
specifications. If API's cannot be copyrighted they don't have rights
over how we use their specifications. The issue of whether an API can
be copyrighted hasn't been 100% settled.
--
Paul Fisher * [EMAIL PROTECTED]
