<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 05/06/2018 11:34 PM, Ingela Andin
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFj9NSS0g_Gc8fnH3nYm1oeqNniFkBZK=3t7t6ZvBxvUyKEaeg@mail.gmail.com">
<div dir="ltr">Hi!<br>
<div class="gmail_extra"><br>
<div class="gmail_quote">2018-05-04 14:40 GMT+02:00 Mahesh
Paolini-Subramanya <span dir="ltr"><<a
href="mailto:mahesh@dieswaytoofast.com" target="_blank"
moz-do-not-send="true">mahesh@dieswaytoofast.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">To echo Heinz's point, is there a *reason*
for the deprecation?
<div><br>
</div>
<div>Enquiring minds want to know...</div>
<div><br>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Th point is to phase out gen_fsm. The deprecated
warning is important to get new users to choose
gen_statem. Also if you have a living product you will
probably be better of in the long run changing to
gen_statem. This</div>
<div>is not a complicated change and an exampel of how to do
it is given in the gen_fsm manual page. Of course we give
lots of time to adopt. We have no plan of removing the
gen_fsm code swiftly, it is there in 20 and 21. </div>
<div>I can see the deprecating process needs to enhanchend,
and yes it sort of has more that one purpose which seems
to conflict a bit.</div>
</div>
</div>
</div>
</blockquote>
<br>
One thing that might help is if we have the ability to deprecate
types which I entered an entry for at
<a class="moz-txt-link-freetext" href="https://bugs.erlang.org/browse/ERL-335">https://bugs.erlang.org/browse/ERL-335</a> . For example, when all the
time units switched from <span class="pl-c1">a format like
milli_seconds to </span><span class="pl-c1"><span class="pl-c1">millisecond
in Erlang/OTP 20.0 it would have been easier to have a
deprecated type that can be used for an easier to understand
warning. That may seem like a small issue that can be avoided
by switching to other functions or modules, but often changes
don't need to be large for small changes that can be limited to
type changes.<br>
<br>
Best Regards,<br>
Michael<br>
</span></span>
</body>
</html>