From omer.anjum at tut.fi Thu Apr 12 05:54:43 2007 From: omer.anjum at tut.fi (Omer Anjum) Date: Tue Jul 1 03:37:21 2008 Subject: [xsde-users] Urgent Information required Message-ID: <20070412125443.7cy7ug82w0oko04c@webmail.tut.fi> Dear CodeSynthesis I am working on developing an embedded system and I need a C or C++ based XML parser to be integrated in my system. I have memroy constraints to be less then 100Kb. Please tell me how XSDe can be helpful for me in my need. How much size Its footprint normally going to have. Regards Omer From boris at codesynthesis.com Thu Apr 12 07:40:48 2007 From: boris at codesynthesis.com (Boris Kolpackov) Date: Tue Jul 1 03:37:21 2008 Subject: [xsde-users] Urgent Information required In-Reply-To: <20070412125443.7cy7ug82w0oko04c@webmail.tut.fi> References: <20070412125443.7cy7ug82w0oko04c@webmail.tut.fi> Message-ID: <20070412114048.GA31435@karelia> Hi Omer, Omer Anjum writes: > I am working on developing an embedded system and I need a C or C++ > based XML parser to be integrated in my system. I have memroy > constraints to be less then 100Kb. This can mean different things. Is it an executable size or runtime memory usage? Runtime memory usage can further be divided into dynamic memory usage and stack usage. > Please tell me how XSDe can be helpful for me in my need. How much size > Its footprint normally going to have. It depends how large is your vocabulary and what features you are using. There was a recent post about this with some numbers that you may find useful: http://www.codesynthesis.com/pipermail/xsde-users/2007-March/000002.html hth, -boris -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 652 bytes Desc: Digital signature Url : http://codesynthesis.com/pipermail/xsde-users/attachments/20070412/2741970a/attachment.pgp From boris at codesynthesis.com Mon Apr 16 04:05:10 2007 From: boris at codesynthesis.com (Boris Kolpackov) Date: Tue Jul 1 03:37:21 2008 Subject: [xsde-users] Urgent Information required In-Reply-To: <20070416041142.p50wfwv3swksgw8g@webmail.tut.fi> References: <20070412125443.7cy7ug82w0oko04c@webmail.tut.fi> <20070412114048.GA31435@karelia> <20070416041142.p50wfwv3swksgw8g@webmail.tut.fi> Message-ID: <20070416080510.GA9961@karelia> Hi Omer, I've CC'ed the xsde-users mailing list to my reply so that others can benefit from this information. Omer Anjum writes: > Thanks for such valuable information to me. One more question i want > to ask is that as at the moment I am interested in the size of XSDe > code i am going to burn in my system memory. It seems to be 250 and > 222Kb. Is it possible to reduce it further to less then 100Kb. It could be possible if your toolchain generates a much tighter code than the vanilla g++-2.95 which was used to obtain these numbers. It also depends on what kind of vocabulary you are planning to handle. For example, a validating executable for a very simple vocabulary (see examples/cxx/parser/minimal) compiled with eVC++ 4.0 is 120Kb. I think if you disable validating it will get below 100Kb. With g++-2.95, however, I don't think it will be possible. Just a conforming non-validating XML parser with a simple SAX interface will be greater than 100Kb, let alone schema validation and data binding. hth, -boris -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 652 bytes Desc: Digital signature Url : http://codesynthesis.com/pipermail/xsde-users/attachments/20070416/4425e68b/attachment.pgp