I couldn't get my script to compile in the editor for the life of me until I figured out I was only using \n as my line endings (developing on a Mac atm). It seems a bit weird that the line endings alone could prevent Galaxy code from compiling.
Edit: maybe not, but it does completely screw up the compile checker's line-by-line error reporting.
I believe Blizzard does most of their development in a windows environment, so they just natively expect crlf. I wouldn't be surprised if this changes due to their statement that they intend to get the editor working in the mac environment
I couldn't get my script to compile in the editor for the life of me until I figured out I was only using \n as my line endings (developing on a Mac atm). It seems a bit weird that the line endings alone could prevent Galaxy code from compiling.
Edit: maybe not, but it does completely screw up the compile checker's line-by-line error reporting.
I believe Blizzard does most of their development in a windows environment, so they just natively expect crlf. I wouldn't be surprised if this changes due to their statement that they intend to get the editor working in the mac environment
Well for now I'm solving the problem with unix2dos or svn propset eol-style: CRLF. Not a big deal anyways.