std.json parsing real numbers.

[Nick Sabalausky]

On Thu, 08 Aug 2013 20:46:15 +0200
"Borislav Kosharov" <boby_dsm at abv.bg> wrote:

> On Thursday, 8 August 2013 at 16:05:56 UTC, Nick Sabalausky wrote:
> > On Thu, 08 Aug 2013 17:20:16 +0200
> > "Borislav Kosharov" <bosak at gmail.com> wrote:
> >
> >> On Thursday, 8 August 2013 at 10:13:51 UTC, khurshid wrote:
> >> >
> >> > I wrote not a "1.24E+1", a "1     .24E     +1"  with leading 
> >> > spaces.
> >> 
> >> Well what should it be if it's not 12.4?
> >
> > A syntax error.
> 
> I don't think this would cause any problems. It would just throw 
> syntax error because there is white-space between? It would be 
> just annoying to get syntax error because of extra white-space.
> 
> Maybe this is one of the situations where we should think "It's 
> not a bug, it's a feature!"
> 
> Unless there is a situation that would make no sense to work or 
> something, it should be left like it is now.

Specs should be adhered to strictly. Otherwise you can wind up in the
"antirobustness principle" situation like late 90's HTML. Laxness
begets more laxness...and then incompatibility bugs.