Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Using LF (\n) instead of CRLF (\r\n) causes some parsing errors. #396
Ran a tool on my code which, among other things, replaced all file endings with LF.
Example of an error:
Complete list of files that gave an error:
Windows8x64 MIT 3.0 with no changes except line endings.
No no it was after downloading with GitHub, initially it ran fine. Then I ran a tool that changed all line endings and then the script parsing errors came.
Should be fixed tho, while it's not an issue for Windows users, it might be more comfortable for linux users to be able to write their scripts with LF line ending.
Yeah, github changes things, you actually have to force it to not do it. We had the same issue in another GIT I run. It was causing script errors in that system as well making merges fail (on a windows box). I would be careful of any tool that does this and manually make the changes on the files using something like Notepad++ and replace statements.
This was observed in the linux work. I'll look at the compiler and see if it's an easy change.
So I'm guessing the error occurs somewhere else, since this looks to me like it should handle both
@eightyeight Sorry, I completely forgot about this thread.
Yes this error occurs every place where you have something on this form:
It has to be
with nothing else on that line, i.e.
does not trigger the error.
I went through every instance of /// comments and it's a consistent error, nicely spotted.
referenced this issue
May 10, 2014
don't know regular expressions much, but what I'm assuming is that the regular expression requires at least 1 character after the 3 slash marks in order for it to compile from what I see, the regular expression: