Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standard Translation Framework #2

Open
GoogleCodeExporter opened this issue Mar 14, 2015 · 0 comments
Open

Standard Translation Framework #2

GoogleCodeExporter opened this issue Mar 14, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

Smali/BakSmali, ApkTool, and related systems need to establish a 
comprehensive standard data format so that version dependent and host 
dependent issues such as android sdk failing to be stable do not effect 
the recoverability and portability of existing and future tools. Their 
interdependency is obvious and should be merged/standardized, but inline 
trace and runtime verification should be handled on-board as should an 
api/interface to standard data for visualization and editing. There is no 
reason a client wishing to use (restrict) only one application should have 
anything else running or accessable on the machine, full decomp-inline-rip-
optimize and rewrite core with tool is an easy target for these projects.

I am more concerned with code audit and on-board compiler and system 
visualization especially when the host changes so severely due to 
Google/etc's incompetence.

Original issue reported on code.google.com by [email protected] on 25 Apr 2010 at 1:48

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant