12 Aug 21:35
Decisions to be taken
From: Erik Huelsmann <ehuels <at> gmail.com>
Subject: Decisions to be taken
Newsgroups: gmane.editors.j.devel
Date: 2008-08-12 19:39:22 GMT
Subject: Decisions to be taken
Newsgroups: gmane.editors.j.devel
Date: 2008-08-12 19:39:22 GMT
Well, it seems there are a number of decisions which need taking. I'll put my position forward on each of them below; if you don't agree, that's fine, however you'll need to speak up for me to know(Continue reading)* Minimal supported Java version Since J2SE 1.5.0 was released 4 years ago next month, I propose to use that as the minimal version * Annotations (@... codes such as @Override) I mainly use the NetBeans IDE for development, which complains about these missing. Since I do see some value in having them, my general idea is they should be inserted. * Code compilation (warnings) Generally, all code - if possible - should compile without warnings. This means that the interpreter will need to be patched in 64 locations to eliminate the "unchecked" warnings * ANSI compliance In general, patches should increase ANSI compliance, or have no impact on it at all (monotonically non-decreasing) The way to test this is by using pfdietz's CL ANSI compliance test suite, just like ECL (and possibly SBCL) does. I mailed pfdietz asking him where the test suite is currently being maintained. * Releases I'm a strong proponent for doing releases, preferably regularly.
* Minimal supported Java version
Since J2SE 1.5.0 was released 4 years ago next month, I propose to
use that as the minimal version
* Annotations (@... codes such as @Override)
I mainly use the NetBeans IDE for development, which complains
about these missing.
Since I do see some value in having them, my general idea is they
should be inserted.
* Code compilation (warnings)
Generally, all code - if possible - should compile without warnings.
This means that the interpreter will need to be patched in 64
locations to eliminate the "unchecked" warnings
* ANSI compliance
In general, patches should increase ANSI compliance, or have no
impact on it at all (monotonically non-decreasing)
The way to test this is by using pfdietz's CL ANSI compliance test
suite, just like ECL (and possibly SBCL) does.
I mailed pfdietz asking him where the test suite is currently being
maintained.
* Releases
I'm a strong proponent for doing releases, preferably regularly.
RSS Feed