Whatever tag numbering scheme we do will have to move up by two, since CONSTANT_Module_info.tag = 19 and CONSTANT_Package_info.tag = 20.
I think we can take our next node at tag 21, for CONSTANT_Q or CONSTANT_Value or whatever we were calling it on Wednesday. I particularly like your ClassType_info; I'd like to use that for MVT, with T_VALUETYPE (14) as the only mode_code that is valid, at first. Later T_OBJECT (12) for symmetry, and T_UNION (3? 16?). (Much much later T_INT or another primitive, associated with a Class, is a very interesting thing to contemplate.) — John On Jun 8, 2017, at 5:00 PM, Dan Smith <daniel.sm...@oracle.com> wrote: > > CONSTANT_PrimitiveType_info { > u1 tag; // 19 > u1 type_code; // 'Z'=90 or 4, 'C'=67 or 5, 'B'=66 or 8, 'S'=83 or 9 > // 'I'=73 or 10, 'J'=74 or 11, 'F'=70 or 6, 'D'=68 or 7 > } > > CONSTANT_ClassType_info { > u1 tag; // 20 > u1 mode_code; // 'L'=76 or 12, 'Q'=81 or 13 > u2 class_index; // Class > }