Prelude.read: no parse on reals with no leading 0 about fortran-src

[mrd]

Yes.. that's why I've been asking around for a function that reads Fortran
literals.

We have the definition within the lexer, but it is not interpreted as a
number.

On Thu, Jul 28, 2016 at 5:09 PM, Dominic Orchard [email protected]
wrote:

Assigned #31 #31 to @mrd
https://github.com/mrd.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#31 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAQmOBLZBVORpvm4r2zsPW9b_oQ-aAqTks5qaNQhgaJpZM4JXYQp
.

[madgen]

It shouldn't be interpreted as a number in the source tree. An external routine is probably the best option.

[mrd]

What do you mean by external? It doesn't have to be interpreted as a number in the source tree, but if I'm going to write a function that follows the literal rules of Fortran grammar, where else would I put it but in fortran-src?

[madgen]

Yeah, yeah. I meant not stored in the AST.

[mrd]

I believe that it is possible to reuse Alex for this purpose, as I'd rather not drag in another dependency on a regex library, and anyway it's best to share the same definition as the regular lexer. So I'll look into it later.

[mrd]

BTW, this should have been a bug in camfort since the specific call to 'read' was in camfort.

And it's fixed now.