Feature print bed #91
Open
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
A pre-release version of libgtftk
A README.md file has been added to master (hotfix).
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.
Hi,
I wrote a new command that print the GTF as BED. The user can pass a set of keys that are concatenated to become the 4th column. If you have time to review... (it pass all the test on the Python side). I'm not convince by "char *keys_concat = (char *)calloc(5000, sizeof(char));" in column.c. I tried to allocate and reallocate after concatenating the string but end up with a segfault. I told myself that column 4 of the bed file rarely goes beyond 5000 char. But If you have a better way (I guess).
Best