3 Commits
Author SHA1 Message Date
Vladimir Panteleev e2dbee2e2a Add Changelog 2010-11-11 23:42:54 +02:00
Vladimir Panteleev 66bccc6a6f Disassemble doubles with adequate precision 2010-11-11 23:25:00 +02:00
Vladimir Panteleev 22194e5baf Documentation: Markdown fixes 2010-11-09 03:41:21 +02:00
3 changed files with 41 additions and 7 deletions
+36
View File
@@ -0,0 +1,36 @@
RABCDAsm Changelog
==================
RABCDAsm v1.3 (2010.11.11)
--------------------------
* Fixed double precision problem
* This also fixes problems with illegal default values for function
parameters (default values for integer parameters are stored as doubles,
which might become out-of-range due to inadequate double precision)
* Added Changelog
* Documentation markdown fixes
RABCDAsm v1.2 (2010.11.06)
--------------------------
* Fixed ref generation for orphan objects which were only referenced
by other orphans
* Better error handling in `abcexport`; warn when no DoABC tags found
* Documentation updates
RABCDAsm v1.1 (2010.06.30)
--------------------------
* Private namespaces are now referenced by auto-generated names
* Use `:` to delimit namespace and name in QNames for consistency
* Warning: this breaks compatibility with v1.0 disassemblies
* Fixed relative include paths
* Add optional byte offsets to labels, which allows lossless representation
of jumps inside instructions and outside the function bounds
* Documentation updates
RABCDAsm v1.0 (2010.05.05)
--------------------------
* Initial release.
+4 -6
View File
@@ -297,9 +297,9 @@ be instantiated in two ways:
although variables are defined using a string syntax, they are not
inserted as a string using this syntax. Thus, the code:
#set str "Hello, world!"
...
pushstring $str
#set str "Hello, world!"
...
pushstring $str
will expand to `pushstring Hello, world!`, which will result in an error.
To correct the problem, add escaped quotes around the variable contents
@@ -423,8 +423,6 @@ Limitations
* Metadata is currently ignored. I haven't noticed any metadata blocks in any
SWF files I've disassembled.
* Floating point numbers may not be disassembled with adequate precision.
* `rabcasm` may create a broken file due to not ordering classes by ancestry.
The problem originates from the fact that a class's ancestors (extended
@@ -435,7 +433,7 @@ Limitations
of order. This results in a file that, when opened, will fail to load with
an error message similar to:
`VerifyError: Error #1014: Class AncestorClassName could not be found.`
VerifyError: Error #1014: Class AncestorClassName could not be found.
The simple work-around is to re-order the classes as they are declared in
the `.main.asasm` file, and place ancestors before descendants.
+1 -1
View File
@@ -416,7 +416,7 @@ final class Disassembler
if (v == ABCFile.NULL_DOUBLE)
sb ~= "null";
else
sb ~= .toString(v);
sb ~= format("%.18g", v);
}
void dumpString(StringBuilder sb, string str)