aboutsummaryrefslogtreecommitdiff
path: root/TODO.md
diff options
context:
space:
mode:
authorfusion32 <marcopuzziello@gmail.com>2025-06-20 06:00:16 -0300
committerfusion32 <marcopuzziello@gmail.com>2025-06-20 06:00:16 -0300
commitd3b92e110a06c6bb2bc0214319b390059bdf7c4a (patch)
tree51293060ad930091625645cc62a1df26eb90fa59 /TODO.md
parentbd3a6a04601749cbde007eaabf803fb602ee2783 (diff)
downloadgame-d3b92e110a06c6bb2bc0214319b390059bdf7c4a.tar.gz
game-d3b92e110a06c6bb2bc0214319b390059bdf7c4a.zip
more work on `communication.cc`
Diffstat (limited to 'TODO.md')
-rw-r--r--TODO.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/TODO.md b/TODO.md
index c623139..b347d45 100644
--- a/TODO.md
+++ b/TODO.md
@@ -23,6 +23,8 @@ I'm not sure whether synchronization is done properly. The implementation of the
## Threading
After some initial dive into `communication.cc`, it has become clear that the original codebase relied on `LinuxThreads` which, among its quirks, assigns different PIDs to different threads, explaining the usage of `getpid()`. It also seems it could lack automatically managed thread stacks which explains `CommunicationThreadStacks`.
+We'll have to address this BEFORE trying to run the server.
+
## Estimate
The decompiled file has ~115K lines of C. If we take ~15K lines to be rubbish, this can be round to ~100K. Considering a low estimate of 200 lines per day, the whole process could take up to 500 days which is quite a bit but not impossible. Now considering a high estimate of 1K lines per day, it could take 100 days which is also quite a bit.