Address OTP24 warnings, ct and eunit paths #334
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This PR is now merged into #336 |
|
Many thanks. :)
BR,
Ulf
…On Tue, May 25, 2021 at 12:43 PM Martin Sumner ***@***.***> wrote:
This PR is now merged into #336
<#336>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#334 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABHDWDFDVZVUXLQICHLRMTTPN5OHANCNFSM45CC5OKQ>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
OTP 24 introduces some new warnings. Also, the
platform_defineregexp forfsm_deprecatedwas extended.Some CT and EUnit options added to the rebar.config to ensure that tests can be run (some eunit tests failed - not sure if caused by some of the code changes to eliminate warnings, i.e. reuse of variables with '_' prefix).