Re: Back from vacation/Status (1.4 Throwable and java.util.prefs)

[Mark Wielaard]

Hi,

On Mon, Sep 03, 2001 at 01:57:48PM -0400, Brian Jones wrote:
> Mark Wielaard <address@hidden> writes:
> 
> > Do we have a list of VMs, what version of
> > Classpath they work with and some build instructions?
> 
> No, it's TBD before 0.03.  The archives have various messages where
> people indicate this.  Some of the VMs are listed on our website.  At
> the moment each tends to distribute their own version of classpath.
> This should be fixed to make things easier for users.
OK. I will go through the archive and try to make a list.

Do you have a list of tasks to be done for 0.0.3?
At the moment I am working on new classes and functionality (Throwable
chaining and prefs) but if we are working towards a new release that might
not be the most productive. What can I do for the release?

> > I have a partial implementation of the new 1.4 java.util.prefs package.
> > It is missing event support and a real backend. There is only a memory based
> > backend at the moment. I can export and import the preferences to and from
> > files so it shouldn't be to hard to implement the file based backend. The
> > only problem with the exporting and importing of the preferences nodes is
> > that I did a quick hack to write/read the XML format by hand. Since I don't
> > know XML that well and I do no escaping of CDATA at the moment it breaks as
> > soon as a key or value contains a ", < or > character. I must look at the
> > JAXP implementation of the ClasspathX project to see if we can use that.
> > I will checkin what I have at the moment later today.
> 
> We'll have to make sure we aren't trying to build this if it isn't
> supposed to work yet.
OK. I will add the classes to the standard.omit list. Is that enough?

I do want to enable them as soon as I have implemented the event support.
Even though the current backend is only memory based and importing and
exporting only works if the keys/values don't contain 'strange' characters,
it does work correctly otherwise.

Cheers,

Mark
-- 
Stuff to read:
    <http://www.toad.com/gnu/whatswrong.html>
  What's Wrong with Copy Protection, by John Gilmore