[erlang-questions] Erlang 21, Stability and the murder of an innocent Statemachine

[Heinz N. Gies]

I have thought of that but I don’t think that’s a real option. Deprication warnings are important, this would turn all of them off which doesn’t help code quality. I want to know if something is deprecated and fix it in most cases. But as Karolis pointed out, it’s easy for a function or two but for a whole behaviour it’s nearly impossible.

It basically creates two erlang worlds, pre-statem and post-statem.

The stack trace is not great but it’s not as bad, it’s somewhat possible to just wrap the whole function calling it into a ifdef and call it a day. Not great it still is a decent amount of code duplication but it’s possible. https://github.com/Kyorai/clique/commit/b0e89de3cbb56396b59a1023903c7259ec2ef145#diff-7a19efbe2afedfb64aa7ec6690e9a13e <https://github.com/Kyorai/clique/commit/b0e89de3cbb56396b59a1023903c7259ec2ef145#diff-7a19efbe2afedfb64aa7ec6690e9a13e> would be an example. It’s more annoying then other changes but not nearly as bad as the gen_fsm

> On 4. May 2018, at 13:58, Roger Lipscombe <roger@REDACTED> wrote:
> 
> On 4 May 2018 at 12:07, Karolis Petrauskas <k.petrauskas@REDACTED <mailto:k.petrauskas@REDACTED>> wrote:
> I agree with Heinz. The deprecation of gen_fsm forced me to stuck on OTP 19 and I dont see any reasonable path to upgrade.
> 
> We upgraded successfully to OTP 20 (and compiled against OTP 21) by simply adding the following to the top of our gen_fsm modules:
> 
> -compile([nowarn_deprecated_function]).  % gen_fsm is deprecated; use gen_statem
> 
> It'll be a problem when gen_fsm is *removed*, but until then, we'll stick with this.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20180504/eb69c0d8/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20180504/eb69c0d8/attachment.bin>