aboutsummaryrefslogtreecommitdiff
path: root/TODO.md
diff options
context:
space:
mode:
authorfusion32 <marcopuzziello@gmail.com>2025-06-23 06:34:16 -0300
committerfusion32 <marcopuzziello@gmail.com>2025-06-23 06:34:16 -0300
commitbdfcbb2f0edee2679bfe588df55e9f99bd837510 (patch)
tree4aea2b1039ea4988debd054c024eefe9c3021dc4 /TODO.md
parentc4dfe97e95846b43c578b3be35d0ef69f9b50e94 (diff)
downloadgame-bdfcbb2f0edee2679bfe588df55e9f99bd837510.tar.gz
game-bdfcbb2f0edee2679bfe588df55e9f99bd837510.zip
`receiving.cc`
Diffstat (limited to 'TODO.md')
-rw-r--r--TODO.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/TODO.md b/TODO.md
index 19e483f..c389567 100644
--- a/TODO.md
+++ b/TODO.md
@@ -8,6 +8,11 @@
- WRITER.CC
- DBFUNCS.CC
+- Include `x == 0xFFFF` inside `CheckVisibility`?
+- The map container uses type id zero but it seems to also be used as a "no type"
+ id which makes me want to add some `isNone()`, `isNull()`, `isVoid()` check to
+ `ObjectType` to be used as an alias when pertinent.
+
## Stack allocations
Any functions that use `alloca` or some other form of dynamic stack allocations will cause decompiled functions to be an absolute mess. It usually shows up in the decompiled code as both a size computation like `-(VAR + CONST & 0xfffffff0)`, followed by some assignment. It doesn't make total sense without looking at the disassembly. I've encountered ~30 such computations and expect the functions containing them to be amongt the most challenging/annoying to be properly decompiled.