How very interesting - but tell me, why did you decide to use the Output stream operator for Input as at first look that appears counterintuitive to me?
Regards, Paul Bandler Nomura International Plc +44 (0)20 7521 3628 [email protected] -----Original Message----- From: Mathieu Champlon [mailto:[email protected]] Sent: 29 November 2010 14:49 To: [email protected] Subject: [ANN] xeumeuleu Hello everyone, For a few years I have been developing a library on top of Xerces : http://xeumeuleu.org I am announcing this now because it has made my life (and the lives of my co-workers and friends) so much easier when working with XML that it might prove useful to others as well. The library can be briefly described as a wrapper above Xerces to provide a C++ stream-like interface. As a quick code sample consider the following XML document : <document> <element name="my element" /> <another-element>42</another-element> </document> The code to read it would be along : std::string name; int content; xml::xifstream xis( "my_document.xml" ); xis>> xml::start( "document" ) >> xml::start( "element" ) >> xml::attribute( "name", name ) >> xml::end >> xml::content( "another-element", content ); Thus simple, compact and flexible code is one of the benefits. There is however a little more to it as it also yields features like easily merging, buffering or manipulating XML chunks. The library is being used in dozens of projects at my company and some interesting patterns seem to emerge when solving real world problems. Well, of course being the author I am totally biased, still if only for the sake of curiosity, check out the documentation at http://xeumeuleu.org I understand that making announcements about a project external to Xerces, even if somewhat related, on this mailing-list might be inappropriate. If this is the case I apologize and won't be doing it again in the future. Regards, MAT. This e-mail (including any attachments) is confidential, may contain proprietary or privileged information and is intended for the named recipient(s) only. Unintended recipients are prohibited from taking action on the basis of information in this e-mail and must delete all copies. Nomura will not accept responsibility or liability for the accuracy or completeness of, or the presence of any virus or disabling code in, this e-mail. If verification is sought please request a hard copy. Any reference to the terms of executed transactions should be treated as preliminary only and subject to formal written confirmation by Nomura. Nomura reserves the right to monitor e-mail communications through its networks (in accordance with applicable laws). No confidentiality or privilege is waived or lost by Nomura by any mistransmission of this e-mail. Any reference to "Nomura" is a reference to any entity in the Nomura Holdings, Inc. group. Please read our Electronic Communications Legal Notice which forms part of this e-mail: http://www.Nomura.com/email_disclaimer.htm
