A few missing "SWMAX" ... (confer issue #334)
add a JSON definition for endpoint specifier keywords
Merge pull request #337 from andlaus/add_endpoint_specifiers

add a JSON definition for endpoint specifier keywords
Merge pull request #336 from osae/fix_smax

A few missing "SWMAX" ... (confer issue #334)
ParserDoubleItem: Fix typos in exception message
Merge pull request #341 from andlaus/fix_typos_in_error_message

ParserDoubleItem: Fix typos in exception message
Parser: rename the internal parseStream() method to parseState()

there is still the public variant of Parser::parseStream() which
parses an arbitrary std::istream. the name of the state-taking variant
was just confusing, IMO...
ParserState: make it possible to detect if initialization went wrong

this is required to get meaningful error messages if the file
specified by INCLUDE does not exist.
Merge pull request #348 from andlaus/ParserState_improve_construction_failure_detection

ParserState: make it possible to detect if initialization went wrong
ParserKeyword: fix typos and improve exception messages
grid property modifier keywords: make the box specifiers optional for all of them

this means adding defaults to EQUALS and COPY. While at it use -1 as
the default value for boxes in all of these keywords...
also eat keywords containing lowercase letters

The Norne deck actually exhibits this atrocity in form of the
'fluxnum' keyword in the file 'INCLUDE/PETRO/FLUXNUM_0704.prop'.

I don't know if Eclipse cares about the case of the keywords, but
opm-parser currently does for sure. (If Eclipse turns out to be
case-insensitive, the easiest fix for us is to just make all keywords
ALL_UPPERCASE...)
Merge pull request #351 from joakim-hove/cherry-pick-339

Cherry pick from #339
Revert "also eat keywords containing lowercase letters"

this was inadvertedly merged. the real fix is to make the parser
case-insensitive...
make the parser case-insensitive

i.e., make keywords ALL_UPPERCASE before using them because Eclipse
seems to be case-insensitive (although this is one of its undocumented
features...)
Merge pull request #349 from andlaus/make_it_case_insensitive

make the parser case-insensitive
EclipseState: make it instantiable without a grid

instead of throwing, we now add a warning to the parser log...
EclipseState: make specifying anything which requires a grid an error if no grid could be instantiated
Split EclipseGrid in dimensions and cell info.

In many cases the only required information in an EclipseGrid instance
is the cartesian dimensions. To facilitate simpler testing - and not
have to create a full dummy grid the dimensions have been internalized
as a separate nx,ny,nz triplet. With this commit it is possible to
instantiate a grid with only dimensions, and no underlying ecl_grid_type
pointer.
Using shared_ptr<EclipseGrid> instead of bare EclipseGrid *