Re: new kawa snapshot 1.6.90

[Chris <chris at bitmead dot com>]

The Java2 Collection classes are available for Java1. Therefore
I suggest you assume Java2, and if you've got Java1 - well you're
just going to have to download the Java2 Collections for Java1.
What's the problem with that?

Per Bothner wrote:

> "Nic Ferrier" <nferrier@tapsellferrier.co.uk> writes:
> 
> 
>> What about shipping GNU-Classpath's implementation of the Collection
>> classes.
>> 
>> Here's how you might do that:
>> 
>> - use a version of the Collection classes moved into a different
>> package, eg: gnu.util
>> - have your sed script build against: either java.util or gnu.util
>> for collection classes
>> - for windows ship the java files built against the gnu.utils
>> classes
> 
> 
> I don't see the it is worth adding the extra code and complication.
> Nothing in Kawa *depends* on the standard collection classes - in fact
> gnu.lists can *replace* the collection classes (at least part).  It is
> just that if you have code that expects a java.util.List instance, you
> would be able to pass it (say) a gnu.lists.FVector (a Scheme string)
> only if Kawa were configured to assume Java2 collections.