Deprecate GtFeatureStream, replace with GtFeatureInStream #68
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
Simply doing a typedef of gt_feature_in_stream_new to gt_feature_stream_new was gave the desired functionality, but did not generate the desired (HTML) documentation. Thus the trivial constructor implementation.
|
maybe there should be something in the docu-system for functions marked as deprecated and functionality to recognize typedefed functions as new functions. |
Garonenur
added a commit
that referenced
this pull request
Aug 27, 2013
Deprecate GtFeatureStream, replace with GtFeatureInStream
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.
Addresses comments raised in #56. Simply doing a typedef of
gt_feature_in_stream_newtogt_feature_stream_newgave the desired functionality, but did not generate the desired (HTML) documentation. Thus the trivial constructor implementation.As far as region node ranges, the default functionality is probably sufficient. I'll worry about providing the option for
gt_feature_index_get_orig_range_for_seqidif the need ever arises.