Intenal Object format
|
07-30-2021, 03:24 PM
Post: #2
|
|||
|
|||
RE: Intenal Object format
I'll take the silence to mean no. So for the record here is what I have so far. Note that there is the in-memory layout and the serialized layout on disk. Differences are pointed out where relevant. Data is stored on disk in little-endian format
The basic layout for all objects is: Code:
In the serialized format, reference count values of 0xFFFF and 0xFFFE sometimes act as special indicators, but I haven't figured them all out yet. Reals: Code:
For sign_stuff 0 = NaN, 1 = normal, 2 = +Inf, -1 = -normal, and -2 = -Inf. Also it lookes like only the top 56 bits of the mantissa are looked at, but I haven't done much digging. Ints: Code:
Strings: Code:
On disk if the ref count = 0xFFFF, or in memory, TSize = uint32_t. On disk if the ref count != 0xFFFF, TSize =uint16_t. Func Calls: This info applies to in-memory format only I haven't looked too much at the serialized format Code:
|
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
Intenal Object format - devin122 - 07-27-2021, 08:57 PM
RE: Intenal Object format - devin122 - 07-30-2021 03:24 PM
RE: Intenal Object format - jfelten - 08-02-2021, 05:15 PM
RE: Intenal Object format - devin122 - 08-04-2021, 06:45 PM
RE: Intenal Object format - rprosperi - 08-04-2021, 07:24 PM
RE: Intenal Object format - Tim Wessman - 08-04-2021, 11:58 PM
RE: Intenal Object format - rprosperi - 08-02-2021, 10:43 PM
|
User(s) browsing this thread: 1 Guest(s)