[erlang-questions] Deprecation warnings: OTP20 and OTP21 compatible code

[Fred Hebert]

I'm one of the few people who actually at times enforces warnings as errors
to dependencies, so that I catch prospective bugs early and can go open
pull requests and patch things to make sure I never get surprised with a
thing that doesn't build through deprecation.

I'd be open to having a mechanism to force-remove it, but I'd be annoyed to
lose the ability to go add it back though.


On Wed, Jun 6, 2018 at 10:30 AM, Bryan Hunt <bryan.hunt@REDACTED
> wrote:

>
> Jose, your pragmatic approach is *very* much appreciated.
>
> *In a top level project*, having explicitly *chosen* to specify the
> `warning_as_errors` option,
> a failed build as a result of warnings is *sensible*.
>
> *In a dependency*, enforcing a top level build failure due to it’s own *deprecated
> code,*
> is at best, *unhelpful*.
>
> While upgrading a project to compile/run on a modern Erlang - it is nearly
> impossible to avoid
> the case where one achieves a successful compilation, yet experience a
> slew of deprecation warnings.
>
> I fork all my dependencies in a non-backward-compatibile way to work
> around this limitation,
> but this approach is less than desirable from the perspective of
> cohesion/fragmentation/anything really.
>
> Bryan
>
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20180606/c758b61d/attachment.htm>