Hey all,

This may be of broader interest.

Cheers, jas.

---------- Forwarded message ----------
From: Jason Stewart <[EMAIL PROTECTED]>
Date: Sep 9, 2006 4:03 PM
Subject: Re: notes from call - xerces-perl status

Hey all,

I've been fantastically busy with xerces lately - things are moving really well.

For many years I have been using SWIG to auto-wrap all the
user-visible C++ classes in Xerces-C to create the Perl API. The
output of SWIG has been a single *very* large C++ file that creates
all the glue code for moving data back and forth between Perl and
Xerces-C. Well, that single file was getting larger and larger as the
API grew, and it has been unmanageable for years, but it finally
become more than I could stomach, so I split it!

This will be a user-visible change because before users could say:

 use XML::Xerces;

and have access to all API classes, but now for example they must use:

 use XML::Xerces::DOM

if they want access to the DOM API.

This means that non-DOM applications will load faster - which for
small CGI scripts that handle XML can be a real issue.

Once I have all the existing tests running 100% correctly again, I
will continue expanding the test cases to cover more of the Xerces
API.

Cheers, jas.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to