I'm sorry I can't help with concrete implementations, but if you're using DOM interfaces, you might consider using the C mapping [1] for DOM IDL [2]. The Xerces C++ DOM interfaces are fairly faithful to the DOM IDL, though some liberties have been taken to remove any CORBA dependencies.
You may, for example, be able to track down an IDL-C compiler, and work from there, and wrap the Xerces implementation from there. In either case, the wrapping should be quite natural, as long as you respect the contract defined in IDL. Sorry I can't be more specific. -Fred [1] http://www.omg.org/technology/documents/formal/c_language_mapping.htm [2] http://www.w3.org/TR/DOM-Level-2-Core/idl-definitions.html Charles McLouth wrote: > I have started a project that I would like to use Xerces for. Due to > the requirements of the bindings I cannot use c++ classes or > exceptions. I must structure a wrapper as a flat c api. Creating > this isn't that complicated, but it is a fair amount of "busy work" > which would result in a lot of code to be tested and debugged. > > I have two questions... > Has anyone create a c binding like this? If one is published it > certainly would reduce my risk. > Regardless of the answer to the first, I certainly see the test > applications in the source tree, but I don't see known inputs and > outputs for the tests. Is there a set of inputs and outputs preserved > in the tree (for regression testing) that I might also leverage? > > many thanks, > > charlie > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
