> IMO the "dumb" part of the parser should just represent this structure > using a convenient C++ API, i.e., the data structure could be > basically a map of stringlists, e.g. > > std::map<std::string, std::vector<string> > That's not nearly enough. By a long shot. First of all, keywords can be repeated, can specify parts of the data in one instance and the rest in another. Or overwrite existing data. Second, keyword data for anything other than mere block properties have (very) specialised formats so teasing it into a list of strings requires at least *some* intelligence. There is also the 'INCLUDE' (and IMPORT) keyword as well as 'PATHS'. Well; I must agree with Bård here. My experience from working with ECLIPSE files (mostly binary, but also some of the .DATA content) is that the amount of special cases, weirdness and surprises is quite large; if you start out with too low level of abstraction on your data structures you will pay for it ☹ Joakim _______________________________________________ Opm mailing list [email protected]<mailto:[email protected]> http://www.opm-project.org/mailman/listinfo/opm ------------------------------------------------------------------- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you
_______________________________________________ Opm mailing list [email protected] http://www.opm-project.org/mailman/listinfo/opm
