Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interger and Float Sizes #18

Open
Aidan63 opened this issue Dec 11, 2022 · 0 comments
Open

Interger and Float Sizes #18

Aidan63 opened this issue Dec 11, 2022 · 0 comments
Labels
Data Model Reading and visualising the targets memory enhancement New feature or request

Comments

@Aidan63
Copy link
Owner

Aidan63 commented Dec 11, 2022

All integer and floats regardless of their size are stored in the same ModelData enum constructor. This means Int64s get truncated and there is no proper structured view of native integers. Might want an optional size argument in the model, where if there is none it a haxe integer / float.

enum IntSize {
    UInt8;
    SInt8;
    UInt16;
    ....
    Unspecified
}

ModelData.MInt(v : haxe.Int64, s : IntSize)

The model should also handled odd types like char, wchar_t, etc.

@Aidan63 Aidan63 added enhancement New feature or request Data Model Reading and visualising the targets memory labels Dec 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Data Model Reading and visualising the targets memory enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant