February 01, 2011
Mark Wielaard: New GPG key.
Finally created a new GPG key using gnupg. The old one was a DSA/1024 bits one and 8 years old. The new one is a RSA/2048 bits one. I will use the new one in the future to sign any release tarballs I might create. pub 2048R/57816A6A 2011-01-29 Key f...
February 01, 2011
Andrew Hughes: [SECURITY] IcedTea6 1.7.8, 1.8.5, 1.9.5 Released!.
We are pleased to announce a new set of security releases, IcedTea6 1.7.8, IcedTea6 1.8.5 and IcedTea6 1.9.5.
This update contains the following security updates:
The IcedTea project provides a harness to build the source code from OpenJDK6 u...
| || || || || || ||1|
|| || || || || || ||
Request for Deprecation of Raw Types and Reification of Generic Types
In the month of June 2009, I did an initial post in the openjdk.java.net-jdk7-dev mailing list with a request for what I feel are two very important changes required in the Java Platform.This resulted in a thread of discussions on the Reification of Generic Types, but lead to no conclusions.Truly, the time is really very much ripe for Reification of Generic Types.The Java Language and Platform Implementers should not really ignore it much longer.
1. Two Most Important Changes Required in Java
1.1 The Requests for Change
1.2 Reason for the Requests
2. Why Reification of Generics was not taken up
2.1 Design Constraints in Section 2.5 of JSR14
3. Hindsight Wisdom: Solutions that could have been
3.1 Dual APIs: Generic and Non Generic Versions
3.2 Why the Dual API solution was not adopted
3.3 Generics right from Java 1.2
4. The Finally Adopted Solution in Java 5.0
5. Why Resurrect the Controversy
5.1 "NO-WIN" situation with No Reification
5.2 Reversal of "NO-WIN" situation with Reification
6.1 Realizing Reification of Generics
6.2 Work involved in the Implementation
6.3 Sign Off Plea
1. Two Most Important Changes R...
Date: May, 27 2010