Spaces:
Running
on
Zero
Running
on
Zero
Commit
·
56d7e86
1
Parent(s):
9bd433d
README
Browse files
README.md
CHANGED
@@ -28,9 +28,7 @@ I'm not a ReSym developer and I may have messed something up. In particular,
|
|
28 |
you must prompt the variable names in the decompiled code as part of the prompt,
|
29 |
and I reused some of their own code to do this.
|
30 |
|
31 |
-
## Oddities
|
32 |
-
|
33 |
-
<details>
|
34 |
|
35 |
### sub_40FD86
|
36 |
|
@@ -57,12 +55,12 @@ seems to be design, so I am doing this too. Otherwise, most of the ReSym
|
|
57 |
examples do not work, because external functions and variables are not properly
|
58 |
declared.
|
59 |
|
|
|
|
|
|
|
60 |
### Other
|
61 |
|
62 |
* ReSym's parser fails for functions with a non-automatic name
|
63 |
-
|
64 |
-
</details>
|
65 |
-
|
66 |
|
67 |
## Todo
|
68 |
|
|
|
28 |
you must prompt the variable names in the decompiled code as part of the prompt,
|
29 |
and I reused some of their own code to do this.
|
30 |
|
31 |
+
## Known Issues / Oddities
|
|
|
|
|
32 |
|
33 |
### sub_40FD86
|
34 |
|
|
|
55 |
examples do not work, because external functions and variables are not properly
|
56 |
declared.
|
57 |
|
58 |
+
Another oddity is that sometimes the field access driver will output a field
|
59 |
+
access expression of `""`. This appears to be a bug in the field access driver.
|
60 |
+
|
61 |
### Other
|
62 |
|
63 |
* ReSym's parser fails for functions with a non-automatic name
|
|
|
|
|
|
|
64 |
|
65 |
## Todo
|
66 |
|