aboutsummaryrefslogtreecommitdiffstats
path: root/erts/obj.debug
diff options
context:
space:
mode:
authorBjörn Gustavsson <[email protected]>2014-03-03 13:50:23 +0100
committerBjörn Gustavsson <[email protected]>2014-03-18 17:47:51 +0100
commitbfe7e45cda6591dc31405ed1be961f079cc541c9 (patch)
tree45c894c1fb3a291d6ab7e5e083b648640554e540 /erts/obj.debug
parentf3cee0e9f409c5850709f11ba15cec22d7387401 (diff)
downloadotp-bfe7e45cda6591dc31405ed1be961f079cc541c9.tar.gz
otp-bfe7e45cda6591dc31405ed1be961f079cc541c9.tar.bz2
otp-bfe7e45cda6591dc31405ed1be961f079cc541c9.zip
Don't fail compilation for modules that contain invalid UTF-8
The default encoding for Erlang modules is now UTF-8, and the compilation would fail if a module contained byte sequences that are not valid UTF-8 sequences. In a large project with say many hundreds of Erlang modules with names of developers such as "Björn" or "Håkan" encoded in latin-1, that could mean that many hundreds of files would need to be modified just to get started testing OTP 17. As a temporary measure to ease the transition, automatically fall back to the latin-1 encoding with a warning for any module that contains invalid byte sequences and for which no encoding has been specified. The intention is to remove this workaround in OTP 18 or 19.
Diffstat (limited to 'erts/obj.debug')
0 files changed, 0 insertions, 0 deletions