> Is that even supposed to work now that UTF-8 is the default?
The README file for 17.0 says:
OTP-11791 The default encoding for Erlang source files is now UTF-8. As
a temporary measure to ease the transition from the old
default of latin-1, if the compiler encounters byte sequences
that are not valid UTF-8 sequences, the compiler will re-try
the compilation in latin-1 mode. This workaround will be
removed in a future release.
It seems like the compiler doesn't retry using latin-1 in this case.
(For the record, the file in question compiles without problems if you
put "%% -*- coding: latin-1 -*-" as the first line.)
On Wed, May 21, 2014 at 1:13 PM, Richard Carlsson
> The attached file (originally an extract from Mochiweb) triggers the
> following problem:
> erlc bar.erl
> /home/richardc/bar.erl:7: cannot parse file, giving up
Thanks for the bug report. I have just merged a fix to the