perlapi/perlintern: Note binary-compatibility-only entries #23332
Conversation
This file contains hidden or 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
Some API elements exist only so that already-existing uses of them can continue to use them without change. Generally newer/shinier methods have come along to accomplish the tasks these do, and new code should use those newer methods. It effectively is deprecated to use these for new code. This commit changes perlapi and perlintern to highlight such elements as not being wise to use going forward. Also, we should feel no pressure to add documention on how to use these elements. The code that already uses them probably already knows how to use them. And if it isn't using them properly, it would be advantageous to convert to use the shinier method, instead of trying to figure out how to get the old one to work. However, this change shows that some elements are wrongly marked as being binary-compatibility only. The list of these needs to examined, and other commits made to remove that marking when appropriate. The list is contained in http://nntp.perl.org/group/perl.perl5.porters/269936
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.
Some API elements exist only so that already-existing uses of them can continue to use them without change. Generally newer/shinier methods have come along to accomplish the tasks these do, and new code should use those newer methods.
It effectively is deprecated to use these for new code.
This commit changes perlapi and perlintern to highlight such elements as not being wise to use going forward. Also, we should feel no pressure to add documention on how to use these elements. The code that already uses them probably already knows how to use them. And if it isn't using them properly, it would be advantageous to convert to use the shinier method, instead of trying to figure out how to get the old one to work.
However, this change shows that some elements are wrongly marked as being binary-compatibility only. The list of these needs to examined, and other commits made to remove that marking when appropriate. The list is contained in
http://nntp.perl.org/group/perl.perl5.porters/269936