<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE chapter SYSTEM "chapter.dtd">

<chapter>
  <header>
    <copyright>
      <year>2021</year><year>2022</year>
      <holder>Ericsson AB. All Rights Reserved.</holder>
    </copyright>
    <legalnotice>
      Licensed under the Apache License, Version 2.0 (the "License");
      you may not use this file except in compliance with the License.
      You may obtain a copy of the License at

          http://www.apache.org/licenses/LICENSE-2.0

      Unless required by applicable law or agreed to in writing, software
      distributed under the License is distributed on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
      See the License for the specific language governing permissions and
      limitations under the License.

    </legalnotice>

    <title>Upcoming Potential Incompatibilities</title>
    <prepared></prepared>
    <docno></docno>
    <date></date>
    <rev></rev>
    <file>upcoming_incompatibilities.xml</file>
  </header>
  <section>
    <title>Introduction</title>
    <p>This document lists planned upcoming potential incompatibilities in
    Erlang/OTP.</p>
  </section>

  <section>
    <title>OTP 25</title>
    <section>
      <title>Distribution flags will become mandatory</title>
      <p>In OTP 25, more <seeguide
      marker="erts:erl_dist_protocol#dflags">distribution
      flags</seeguide> will become mandatory. That is, Erlang nodes
      will refuse to connect to nodes not implementing all of the
      mandatory distribution flags. If you implement the Erlang
      distribution protocol yourself, you will need to implement
      support for all mandatory distribution flags in order to
      communicate with Erlang nodes running OTP 25.</p>
      <p>The following distribution flags will become mandatory in OTP
      25:</p>
      <taglist>
        <tag><c>DFLAG_BIT_BINARIES</c></tag>
        <item>Support for bitstrings.</item>
        <tag><c>DFLAG_EXPORT_PTR_TAG</c></tag>
        <item>Support for external funs (<c>fun Module:Name/Arity</c>).</item>
        <tag><c>DFLAG_MAP_TAGS</c></tag>
        <item>Support for maps.</item>
        <tag><c>DFLAG_NEW_FLOATS</c></tag>
        <item>Support for the new encoding of floats.</item>
        <tag><c>DFLAG_FUN_TAGS</c></tag>
        <item>Support for funs, but only in the new format
        (<c>NEW_FUN_EXT</c>) because <c>DFLAG_NEW_FUN_TAGS</c> is also
        mandatory.</item>
      </taglist>
    </section>
  </section>

  <section>
    <title>OTP 26</title>
    <section>
      <title>The distribution flag DFLAG_V4_NC will become mandatory</title>
      <p>As of OTP 26, the distribution flag <seeguide
      marker="erts:erl_dist_protocol#DFLAG_V4_NC">DFLAG_V4_NC</seeguide>
      will become mandatory. If you implement the Erlang distribution
      protocol yourself, you will need to implement support for
      <c>DFLAG_V4_NC</c> in order to communicate with Erlang nodes
      running OTP 26.</p>
    </section>

    <section>
      <title>The new link protocol will become mandatory</title>
      <p>
	As of OTP 26, the <seeguide
	marker="erts:erl_dist_protocol#new_link_protocol">new link
	protocol</seeguide> will become mandatory. That is, Erlang
	nodes will then refuse to connect to nodes not implementing
	the new link protocol. If you implement the Erlang
	distribution yourself, you are, however, encouraged to
	implement the new link protocol as soon as possible since the
	old protocol can cause links to enter an inconsistent state.
      </p>
    </section>

    <section>
      <marker id="atoms_be_utf8"/>
      <title>Atoms will be encoded as UTF-8 by default</title>
      <p>
	As of OTP 26, the functions
        <seemfa marker="erts:erlang#term_to_binary/1">
        <c>erlang:term_to_binary/1,2</c></seemfa> and
        <seemfa marker="erts:erlang#term_to_iovec/1">
        <c>erlang:term_to_iovec/1,2</c></seemfa> will encode all atoms as
        UTF-8 by default. The current default behavior is to encode atoms as
        Latin-1 if possible.
      </p>
      <p>
	If you implement your own decoding of the Erlang external format you
        must either:
      </p>
      <list type="bulleted">
        <item>
          <p>
            Make sure your implementation supports the UTF-8 encodings
            <seeguide marker="erts:erl_ext_dist#ATOM_UTF8_EXT">
              <c>ATOM_UTF8_EXT</c></seeguide> and
            <seeguide marker="erts:erl_ext_dist#SMALL_ATOM_UTF8_EXT">
              <c>SMALL_ATOM_UTF8_EXT</c></seeguide>.
          </p>
        </item>
        <item>
          <p>
            Call <seemfa marker="erts:erlang#term_to_binary/2">
            <c>erlang:term_to_binary/2</c></seemfa> or
            <seemfa marker="erts:erlang#term_to_iovec/2">
            <c>erlang:term_to_iovec/2</c></seemfa>
            with option <c>{minor_version,1}</c> to force Latin-1 encoding. This
            is a more short-term solution as Latin-1 encoding may be phased out
            and removed in later OTP releases.
          </p>
        </item>
      </list>
    </section>

    <section>
      <title>The default timewarp mode will change to multi-time warp mode</title>
      <p>
	The default <seeguide marker="erts:time_correction#Time_Warp_Modes">
        Time Warp Mode</seeguide> will be changed from
        <seeguide marker="erts:time_correction#No_Time_Warp_Mode">
        no time warp mode</seeguide> to <seeguide marker="erts:time_correction#Multi_Time_Warp_Mode">
        multi-time warp mode</seeguide>. See <seeguide marker="erts:time_correction">
        Time and Time Correction in Erlang</seeguide> for details on how this will
        effect your system.
      </p>
    </section>

  </section>
</chapter>
