Strict mode parses invalid json.

[ya1gaurav]

[]An error has occurred.

Jsoncpp strict mode is able to parse above input.
This is invalid json but somehow passed by latest jsoncpp code till "]". It is not considering input after "]".

Sample code :

int main()
{
Json::Value root;

ifdef STRICT
Json::Reader reader(Json::Features::strictMode());

else
Json::Reader reader;

endif
std::ifstream file("test_now.json");

bool parsingSuccessful = reader.parse(file, root);

if(!parsingSuccessful)
{
        cout << "Failed to parse configuration. " << reader.getFormatedErrorMessages();
        return 0;
}
else
        cout << "Pretty-Print: " << root.toStyledString() << endl;

}

Output with all & strict mode:
./all
Pretty-Print: []

./strict
Pretty-Print: []

[ya1gaurav]

Input Json:
std::string input_param = "[]An error has occurred.";

[cdunn2001]

That seems ok. It found a valid JSON document and stopped parsing.

I guess we should make the string-version throw an exception, if that's not too hard. But the stream version is correct; it will leave the extra characters on the stream. Right?

[ya1gaurav]

The problem occur in both cases if i give input using ifstream form file or as std:string input.

[cdunn2001]

I disagree that it's an error for ifstream. As long as it doesn't actually consume the extra characters, the behavior is correct for streams.

[ya1gaurav]

So, you mean for above input , below output is correct & desired ?
./all
Pretty-Print: []

./strict
Pretty-Print: []

[cdunn2001]

For a string, it can be considered an error. For a stream, the extra data can be considered as part of the next message.

[ya1gaurav]

So, string case need to be modify to report error ?

[cdunn2001]

Yes. But we might break existing use-cases. So I think we have to consider it a feature now. Sorry