Jason

You've gotten me back into the human race. This I would be interested in.

Paul


>
>
> Everyone-
>
>
> I have a proposal for the Wing Ding: Scrub the JDK.
>
> I've been intrigued George's pair-programming group. I'd like to get
> some hand's on experience with the new language features in Tiger (JDK
> 1.5). Lastly, I'm also very keen to somehow shame Sun into improving
> the JDK.
>
> Here's Plan A, based on Tiger:
>
> - We all have to sign the research license.
>
> - Meet on a very regular basis.
>
> - Use whatever XP, Agile, or Super Duper methodology stuff we think
> might help.
>
> - Set up private Subversion source repository.
>
> - Choose two or three modest yet representative open source projects
> to keep in sync with the morphed JDK. Maybe Jetty and JEdit.
>
> - Use software quality tools, such as code coverage, auto bug
> finders, unit test harnesses.
>
> - Prioritorize our efforts. Here's some candidates.
>
> - Eliminate dead-code, duplicate code, deprecated stuff.
>
> - Best of breed collections library
>
> - Remove unnecessary synchronization
>
> - Unify event dispatch (e.g. listeners held with weakrefs)
>
> - Hook up code pretty printer to source control.
>
> - Progress reports every 3 or 4 months.
>
>
> Plan B is same as above, but based on GNU's Classpath Project.
>
>
> Pros for Plan A is to use latest, greatest language. Cons is that we
> couldn't share the results openly nor use the results in future works.
> Pros to Plan B is it already has a head start.
>
>
>
>
> Cheers, Jason Aaron Osgood / Seattle WA
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>