Lately I've been told at work to use a library in C. Most calls have the signature ErrorType function(const char *xml);
I have to pass to them xmls of more than two levels deep, attributes, and around ten elements. When I asked why such interface to a library, claiming that it was uncomfortable to me, the lib developer told me that in fact xml-parameter-passing was one of the techniques he liked most, and helped him solve a lot of problems easily. 2007/5/23, Lluís Batlle <[EMAIL PROTECTED]>:
I find that most of the tree-like information I want to store in a fd fits well on OGDL (1st layer). I think Forsyth was working on a OGDL parser in limbo - I don't know if he finished or stopped thinking on it. I wrote my own in c++, and I used a j2me implementation given in the OGDL main site - them both work fine. 2007/5/22, Bruce Ellis <[EMAIL PROTECTED]>: > to throw a spaniard in the works (never was good at mangling metaphors) > i use XML to store midi patches and configs. as a human never edits > them directly (the pre-existing library does that) it was a good choice. > i considerered an ndb approach, and S-expressions, but i like what i got. > > i could have invented a file format and implemented it but i chose not to. > > you wouldn't want to read or write any configuration for something > with a thousand params but programs do it fine. > > brucee > > On 5/23/07, erik quanstrom <[EMAIL PROTECTED]> wrote: > > however, one end would be *heading* north. the other would be > > *heading* south. > > > > - erik > > >
