diff options
| author | fusion32 <marcopuzziello@gmail.com> | 2025-06-17 03:13:05 -0300 |
|---|---|---|
| committer | fusion32 <marcopuzziello@gmail.com> | 2025-06-17 03:13:05 -0300 |
| commit | 56bdec57609cd00d7827a3008a9c6b06707097ca (patch) | |
| tree | 08e42a536bf807842de299047195c9ecf5d526ae /TODO.md | |
| parent | 0612480d9beb19b9e90b3a4f1198b3da1fd21f6a (diff) | |
| download | game-56bdec57609cd00d7827a3008a9c6b06707097ca.tar.gz game-56bdec57609cd00d7827a3008a9c6b06707097ca.zip | |
all `crplayer.cc` functions outside `TPlayer`
Diffstat (limited to 'TODO.md')
| -rw-r--r-- | TODO.md | 12 |
1 files changed, 8 insertions, 4 deletions
@@ -1,16 +1,15 @@ ## TODO NEXT -- OPERATE.CC -- HOUSES.CC - CRPLAYER.CC +- QUERY.CC +- COMMUNICATION.CC +- HOUSES.CC - CRNONPL.CC - MOVEUSE.CC - SENDING.CC - RECEIVING.CC - CONNECTIONS.CC -- COMMUNICATION.CC - READER.CC - WRITER.CC -- QUERY.CC - DBFUNCS.CC ## Stack allocations @@ -19,6 +18,11 @@ Any functions that use `alloca` or some other form of dynamic stack allocations ## Exceptions I didn't dive into how exceptions are handled, but it seems that the ones related to creature actions have the outter most endpoint at `TCreature::Execute`. There can also be some checkpoints in between to modify a `RESULT` value or handle a failure. +## Synchronization +I'm not sure whether synchronization is done properly. The implementation of the first few `crplayer.cc` functions left me with a taste of race conditions although integer loads on x86 are generally atomic. + +I'm also under the impression that `getpid()` is used for retrieving the current thread id, so we'll have to wait and see how things unfold outside the main thread. + ## 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. |
