Hi Gareth, Gareth Reakes <[EMAIL PROTECTED]> writes:
> >If the Xerces-C team thinks it's valuable to include Xerces-P, then it > >will make it into the release. > > I think it is valuable. It is not really a question of whether it is valuable or not but rather of whether there is someone to develop and maintain it in the long term. So far Jason stepped up to get it into the compilable state but nobody committed to maintaining it in the long run. And my understanding is that swig is not something that can just sit there without requiring much attention since it needs updating every time the interface changes. > I think there is a good chance to get further bindings now the > process is easier. As Jason mentioned in one of his emails, he asked a number of scripting language communities whether they would be interested in Xerces-C++ binding. Apparently nobody was interested. My position boils down to the following: if we cannot find a permanent maintainer for swig then we should move it to attic (new SVN module for unused code). Releasing 3.0.0 with swig but without permanent maintainer would give a false impression to the users that this functionality will be maintained and supported in the future. If, at some point, we find someone interested in maintaining swig we can always move it back to the trunk. Boris -- Boris Kolpackov, Code Synthesis Tools Open source XML data binding for C++: http://codesynthesis.com/products/xsd Mobile/embedded validating XML parsing: http://codesynthesis.com/products/xsde --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
