I've used both Java and C# .NET and am a fan of both. I loved Java for
generics in 1.5 and Java still rocks at it. C# .NET then incorporated
that idea, though it's not as programmer-friendly as Java's solution.
I liked the C# .NET bandwagon as the language supported properties - a
replacement for regular get and set methods. I really wish Java would
incorporate it in the next version.
Andrew Thompson - 28 Dec 2006 08:25 GMT
> I've used both Java and C# .NET and am a fan of both. I loved Java for
> generics in 1.5 and Java still rocks at it. C# .NET then incorporated
[quoted text clipped - 3 lines]
> replacement for regular get and set methods. I really wish Java would
> incorporate it in the next version.
The best place to express that might be..
<http://jcp.org/en/home/index>
..or as an RFE through the bug database.
(both of which, others can vote for*, and
Sun might actually be expected to read).
* Assuming they do not vanish into the aether,
as sometimes happens with bug reports - have
not tried the JCP.
Andrew T.
Mike Schilling - 28 Dec 2006 09:13 GMT
> I've used both Java and C# .NET and am a fan of both. I loved Java for
> generics in 1.5 and Java still rocks at it. C# .NET then incorporated
> that idea, though it's not as programmer-friendly as Java's solution.
Really? How are Java's half-assed erased generics friendlier than C#'s
complete implementation?
RedGrittyBrick - 28 Dec 2006 12:14 GMT
>> I've used both Java and C# .NET and am a fan of both. I loved Java for
>> generics in 1.5 and Java still rocks at it. C# .NET then incorporated
>> that idea, though it's not as programmer-friendly as Java's solution.
>
> Really? How are Java's half-assed erased generics friendlier than C#'s
> complete implementation?
Who cares?
Arne Vajhøj - 29 Dec 2006 02:15 GMT
> I liked the C# .NET bandwagon as the language supported properties - a
> replacement for regular get and set methods. I really wish Java would
> incorporate it in the next version.
Why bother ?
It is just get and set with same functionality but different syntax !
It is still coding by convention not something that is enforced by
the language/compiler.
Arne