+1 for (3)
Michael
On 10/17/09 3:55 AM, Uwe Schindler wrote:
Just because I came along a lot of new Generics declarations:
How should we handle generics parameters in the source code? There are more
possibilities:
1. Map
2. Map
3. Map
Sun's Java code in src.jar of their JDK always uses (3)[
+1 for option 3
Mike
On Sat, Oct 17, 2009 at 6:55 AM, Uwe Schindler wrote:
> Just because I came along a lot of new Generics declarations:
> How should we handle generics parameters in the source code? There are more
> possibilities:
>
> 1. Map
> 2. Map
> 3. Map
>
> Sun's Java code in src.jar o
Uwe Schindler wrote:
> Just because I came along a lot of new Generics declarations:
> How should we handle generics parameters in the source code? There are more
> possibilities:
>
> 1. Map
> 2. Map
> 3. Map
>
> Sun's Java code in src.jar of their JDK always uses (3)[only in some special
> cases,
Always used 1.
That's also the default for many autoformatters, which probably
explains why people use it.
On Sat, Oct 17, 2009 at 14:55, Uwe Schindler wrote:
> Just because I came along a lot of new Generics declarations:
> How should we handle generics parameters in the source code? There are m
Just because I came along a lot of new Generics declarations:
How should we handle generics parameters in the source code? There are more
possibilities:
1. Map
2. Map
3. Map
Sun's Java code in src.jar of their JDK always uses (3)[only in some special
cases, when it gets complicated, like when ?
