domxml in PHP5

[email protected] (Christian Stocker)
Newsgroups php.xml.dev
Organization Bitflux GmbH
Message-ID <[email protected]>
Hi

It was very quiet on this list in recent weeks. I was and still am very
busy with other projects. In the meantime Rob Richards jumped on the
bandwagon and provided a lot of memleak fixes for domxml (PHP 4.3.2 will
have all those fixes plus finally domdocument->free() as an userland
method. hooray ;) )

We were discussing by private mail, how we should proceed further. I
think, the goal mentioned in previous mails were pretty much hight to
reach in the time PHP5 will be released. So I suggest, we stick to the
following TODO list for PHP 5.0.0 and try to incorporate the more
advanced feature for a later release. Of course, if there are people who
want to contribute this stuff before, I have no problem with that.

Here's my suggestion (and I think, if there are more people than just me
contributing, we should be able to reach this)

- Go over the whole "memory/free" stuff and clean it up.

- Seperate php_domxml.c in different files. maybe just the different
modules (xslt/xpath/dom/parser/etc..), or maybe even for each class
(document, node, text, etc) a file (not shure, what's more feasible)

- use namespaces. Got already a patch from Tal for that.

- use setters/getters. $domtext->data = "hello" should be possible with
PHP5 (the properties in domxml at the moment are a joke and shouldn't
be used..), this will allow much more dom-compliance

- Implement first most of the dom-standard. Then we add some of the
convenience methods libxml2 has (get_content() et al. They are not in
the dom-standard, but make the life for domxml-programmers a lot easier
and they are also much faster than using the "traditional" dom methods)

- Lastly, if there's time, add as much BC as possible. Or we just
provide a PEAR-wrapper, which makes transition from domxml/PHP4.3 to
domxml/PHP5 easier.

chregu
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.