Vector35 / Vector35/binaryninja-api
Document creating a custom calling convention
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
There are little to no good examples of creating a custom calling convention. We should either create one in the examples and link from the developer docs section or implement one in a blog post as a narrative that can be turned into an entire section in the developer docs.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing examples and the developer docs section to see where custom calling conventions are currently covered. Compare the two proposed paths—an example linked from the developer docs or a blog-post narrative that can become a docs section; done means one of those paths provides a useful custom calling convention example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100