From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: JDK 1.5 beta2 and generics |
Date: | 2004-06-18 16:30:17 |
Message-ID: | Pine.BSO.4.56.0406181124300.7147@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Fri, 18 Jun 2004, Dave Cramer wrote:
> Kris,
>
> How does the 1.3, 1.4 driver handle this ?
In the past they haven't touched the API without a new JDBC version. Our
model handles this cleanly with a separate directory/implementation for
the new part of the API. The problem here is that they have changed the
method signature's specified in an interface without changing the API
version.
Note that this is only a problem for implementors, not callers.
The weak generic type checking allows for instance a method like
func(Hashtable<String,String>) to be called with func(new Hashtable()).
It doesn't require the caller to alter their passed data type only the
implementor to match the stricter method signature.
Kris Jurka
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-06-18 16:32:52 | Re: Nested transactions |
Previous Message | Tom Lane | 2004-06-18 15:38:10 | Re: Nested transactions |