Implement parsers for different item types

Open Razican opened this issue 9 years ago • 1 comments

Here is the tracking issue for parser implementations:

[x] Header
[x] StringIdList
[x] TypeIdList
[x] PrototypeIdList
[x] FieldIdList
[x] MethodIdList
[x] ClassDefList
[x] Map
[x] TypeList
[x] AnnotationSetList
[x] AnnotationSet
[x] ClassData
[ ] Code - No bytecode parsing yet.
[x] StringData
[x] DebugInfo
[x] Annotation
[x] EncodedArray
[x] AnnotationsDirectory

New in version 038:

[ ] call_site_id_item
[ ] method_handle_item
[ ] Values for method handles and method types.

Oct 07 '16 09:10 Razican

This is basically done. Currently the CodeItem bytecode is not being parsed (we only store an array of u16). But we might not even want to, at least in the reading phase. Processing all those u16 as typed bytecode can be a big processing issue, and it should probably only be done if that information is actually required (that's the case in SUPER).

But since this library aims to be usable by anybody, not only SUPER, it might be a big-enough issue. Anyway, it will need to be implemented in any case, even if it's not in the read phase.

Feb 18 '17 21:02 Razican