Code Renderer for Objective-C calls

Open
#5,597 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp, objective-c
Domain
reverse-engineering

Research direction

Start by locating the Objective-C code-rendering entry point that produces message signatures and disassembly names. Compare its output with the requested practical form: implicit self/sel handling, selector arguments inline, and no underscore prefix. Done means the renderer reflects each listed formatting improvement; the issue names no file or test to run.

Written by the indexing model from the issue text.

Description

Component: Objective-C Workflow

It would be nice if the signatures of the Objective-C messages would match more closely their form in practical use/documentation, etc. This is how they look right now:

image

Improvements would be:

  • No _ prefix in the signature
  • Automatic rename of arg1 to self and arg2 to sel in the disassembly
  • Removal of self and sel in the signature (these are implicit)
    • Or only sel for class selectors
  • Selector arguments in-line in the selector, e.g. -[NSView addSubview:(NSView*)arg1], instead of suffixed with ()
Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Vector35/binaryninja-api

All issues in Vector35/binaryninja-api

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.