Hi, On Friday 28 March 2014 11:01:57 Joakim Hove wrote: >>> I guess you could try to delete some of the keywords that create >>> trouble, if they are unneeded and not too many. >> >> Or even better: add the keyword definitions to opm-parser. They are just >> JSON definitions and are located in opm/parser/share/keywords > > In general I agree with Andreas suggestion, but for the particular case > Markus had here the problem was that the new parser is stricter than old, > and at least the BGAS keyword was not correctly formatted in Markus deck > (as I understood it).
hm, okay. does Eclipse accept that particular deck? if yes, it may be a good
idea to also become a bit less strict in opm-parser. (maybe we should just
produce a warning instead of an error?)
cheers
Andreas
--
Never underestimate a C programmer's ability to write C code in any
language you give them.
— Jason Gorman
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Opm mailing list [email protected] http://www.opm-project.org/mailman/listinfo/opm
