This is the mail archive of the
kawa@sources.redhat.com
mailing list for the Kawa project.
Re: new kawa snapshot 1.6.90
- To: "Nic Ferrier" <nferrier at tapsellferrier dot co dot uk>
- Subject: Re: new kawa snapshot 1.6.90
- From: Per Bothner <per at bothner dot com>
- Date: 26 Apr 2001 20:14:32 -0700
- Cc: kawa at sources dot redhat dot com
- References: <sae8d636.066@tapsellferrier.co.uk>
"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.
--
--Per Bothner
per@bothner.com http://www.bothner.com/~per/