diff options
| author | Léo Lam <leo@leolam.fr> | 2021-07-28 12:20:18 +0200 |
|---|---|---|
| committer | Léo Lam <leo@leolam.fr> | 2021-07-28 12:20:53 +0200 |
| commit | ea030c356cf283e5cf0bde58ea08a445504573f4 (patch) | |
| tree | 6f17eb40aeadf5f68f7b9f9616b3ac15c34a3e92 | |
| parent | 1d4c815fbae3daab1d3f1a6d90716fe3e7d183f4 (diff) | |
Contributing: Mention that functions can be stubbed
| -rw-r--r-- | Contributing.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/Contributing.md b/Contributing.md index 7056bb7a..20f32e90 100644 --- a/Contributing.md +++ b/Contributing.md @@ -139,6 +139,7 @@ public: * Keep in mind that decompilers can only produce C pseudocode. Some function calls may be member function calls. * Identify inlined functions and *uninline* them. For example, if you see a string copy, do **not** write the copy loop manually! Instead, call the inline function and let the compiler inline the function for you. * Identify duplicate pieces of code: those are usually a sign that functions have been inlined. + * Non-inline function calls can just be stubbed if you don't feel like decompiling them at the moment. To "stub" a function, just declare the function (and the enclosing class/namespace/etc. if needed) without implementing/defining it. 4. **Build**. 5. **Get the mangled name** of your function. For example, if you are decompiling BaseProcMgr::createInstance: |
