Am 26.08.2014 16:51, schrieb Sönke Ludwig:
Am 26.08.2014 16:40, schrieb Don:
This is the difference: if you get NaN or Infinity, there's probably a
straightforward bug in the Javascript code, but your D code is fine. Any
other kind of JSON parsing error means you've got a garbage string that
isn't JSON at all. They are very different errors.
It's a diagnostics issue.
The error will be more like "filename(line:column): Invalid token" -
possibly the text following the line/column could also be displayed.
Wouldn't that be sufficient?
One argument against supporting it in the parser is that the parser
currently works without any configuration, but the user would then have
to specify two sets of configuration options with this added.
