summaryrefslogtreecommitdiff
path: root/Why-should-I-use-this-over-binary-hacking.md
diff options
context:
space:
mode:
authorThomas Winwood <twwinwood@gmail.com>2020-05-18 14:33:06 +0100
committerThomas Winwood <twwinwood@gmail.com>2020-05-18 14:33:06 +0100
commit0d851590f28dcb22c3ff8a3c5f7124a452984114 (patch)
tree7875040c01d7f745a0546491f38e6477be0b17ec /Why-should-I-use-this-over-binary-hacking.md
parentd001f52bdd2295fef99ba2c795d76e6c8f80029e (diff)
Updated Why should I use this over binary hacking (markdown)
Diffstat (limited to 'Why-should-I-use-this-over-binary-hacking.md')
-rw-r--r--Why-should-I-use-this-over-binary-hacking.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/Why-should-I-use-this-over-binary-hacking.md b/Why-should-I-use-this-over-binary-hacking.md
index 2b1cfc3..18616ef 100644
--- a/Why-should-I-use-this-over-binary-hacking.md
+++ b/Why-should-I-use-this-over-binary-hacking.md
@@ -4,4 +4,4 @@ The decompilation, on the other hand, allows for the use of C code, in writing n
There is also another, if not _the_ most important advantage to using decompilations: **we do not care about offsets**. Unlike binary hacking, one can easily change the size, locations, even the members of variables at their will. The linker (`ld`) does the work for you, recalculating and modifying references to variables. Gone are the days of worrying about remaining free space; we just don’t do that here.
-**Before you start hacking, it is recommended that you have some experience in coding in either: C, C#, Java, or any other C-like programming language, if you want to use use the decompilation.** \ No newline at end of file
+**Before you start hacking, it is recommended that you have some experience in coding in C, C++, Rust, C#, Java, or any other C-like programming language, if you want to use use the decompilation.** \ No newline at end of file