Re: file:read("*n") reference manual entry improvement

[Francisco Olarte <folarte@...>]

Hi:


> I am more and more convinced that the real problem is that the
> implementation has a bug. See the following two cases:
> input   whas was read by '*n'   returned result
> 0x.G    0x.                     0
> 0xG     0x                      nil

If it's using fscanf, this kind of things are usual. It normally uses
just one char lookahead and pushes it back on errors, leading to
bizarre results when errors are deep down, like 1.0E+X, you only
notice the error when reaching the X, but then you've read a lot of
chars.

Francisco Olarte.