__FILE__ breaks if filename contains a quote

[ISSOtm]

That's about it. The quote(s) need(s) to be escaped.

[JL2210]

Fixed by #566
Probably still needs to be implemented in #557

[ISSOtm]

I added a regression test that'll ensure that the new lexer will have to implement it.

[AntonioND]

That's great, and that's why we need more tests. With enough coverage it becomes far less scary to make big changes...

[ISSOtm]

There is however one unintended consequence of adding this test: Windows is not feeling too great about it due to... the quote. I'm not sure how to solve this...

[AntonioND]

I think that we shouldn't have that test, probably. I mean, we should have the test, but the file could be generated by the test scripts, and it could be skipped on Windows. Having weird file names is a bad idea.

[ISSOtm]

Well, I tried generating the test from within the test script, and it somehow still gets generated. How? Beats me. Guess it should only be generated when not on Windows, but how is that detectable reliably? I tried uname, but it returns "MinGW", which is probably not suitable...

[AntonioND]

Oh, of course, you need to skip the test on Windows. I think that using uname and checking for MinGW is fine, actually. We can always add other strings if needed in the future.

[ISSOtm]

Fixed it in 9742fa7, then.