Windows end of line can give issues

[Wulfklaue]

When a file is saved under Windows to WSL, it has the default CRLF encoding instead of the expacted LF.

Compiling this results in:

macro didn't expand to a valid program, it expanded to:

================================================================================
--------------------------------------------------------------------------------
   1. __slang__ << "<html"
   2. __slang__ << ">"
.....
--------------------------------------------------------------------------------
Syntax error in expanded macro: macro_140680034121248:65: expecting '\n' after '\r'

"_slang__ << "Multi-line comment

Might be interesting to also add Windows end of line file support, as Crystal is recently making a lot of process towards a Windows version.

[jeromegn]

That's interesting. I could either detect windows or maybe always use \r\n and there would be no harm?

I need to do some testing.

[jeromegn]

What's an easy way to test this?

I think we were missing this \r\n case in the comment section specifically. I've added it now, can you please test with master?