documentation:tiny2
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
documentation:tiny2 [2023/09/13 18:09] – removed - external edit (Unknown date) 127.0.0.1 | documentation:tiny2 [2023/09/16 21:23] (current) – Add missing inline code markers nebelnidas | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Tiny v2 ====== | ||
+ | Tiny v2 consists of a list of hierarchical sections. Every line starts a new section, whether it continues an existing section is determined by the indentation level. A section' | ||
+ | |||
+ | The child-to-parent relationships form the paths to uniquely identify any element globally. For example, all field and method sections that are children of a class section represent members of the represented class. | ||
+ | |||
+ | Sections need to be unique within their level. For example a specific class may only be recorded once, a comment can't be redefined or the same parameter listed twice. | ||
+ | |||
+ | **Example: | ||
+ | < | ||
+ | tiny 2 0 official intermediary named | ||
+ | someProperty someValue | ||
+ | anotherProperty | ||
+ | c a class_123 pkg/ | ||
+ | f [I a field_789 someField | ||
+ | m (III)V a method_456 someMethod | ||
+ | p 1 param_0 x | ||
+ | p 2 param_1 y | ||
+ | p 3 param_2 z | ||
+ | c Just a method for demonstrating the format. | ||
+ | c b class_234 pkg/ | ||
+ | m (Ljava/ | ||
+ | </ | ||
+ | |||
+ | |||
+ | ===== Grammar ===== | ||
+ | < | ||
+ | < | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | |||
+ | < | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | |||
+ | |||
+ | ==== Notes ==== | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | |||
+ | |||
+ | ===== Miscellaneous Notes ===== | ||
+ | * The encoding for the entire file is UTF-8. Escape sequences are limited to the types, locations and conditions mentioned above. | ||
+ | * Indenting uses tab characters exclusively, | ||
+ | * Sections or properties with unknown types/keys should be skipped without generating an error. | ||
+ | * The amount of extra namespaces defined in the header and the amount of names in every '' | ||
+ | * Sections representing the same element must not be repeated, e.g. there can be only one top-level section for a specific class or one class-level section for a specific member. | ||
+ | * If any variable mapping doesn' | ||
+ | * Mappings without any (useful) names should be omitted. | ||
+ | * Sections without any (useful) mappings or sub-sections should be omitted. | ||
+ | * Comments should be without their enclosing syntax elements, indentation or decoration. For example, the comment < | ||
+ | /** | ||
+ | * A comment | ||
+ | * on two lines. | ||
+ | */</ | ||
+ | |||
+ | |||
+ | ===== Standard Properties ===== | ||
+ | * '' | ||
+ | * '' |