P4
NEWHPROF: Spec out the naming conventions used in the binary format
>
> The third issue is maybe something that would bear mentioning
> in the docs. I've noticed that there are "LOAD CLASS" records
> for array classes, called e.g. "Foo[]" and "char[]". That's
> great (back in the day, no such class objects existed), but
> the fact of their existance isn't documented. Neither is the
> naming convention. This might be a good thing to say, just
> to make sure it doesn't change in the future.
>>>>>> The third issue is maybe something that would bear mentioning>>> in the docs. I've noticed that there are "LOAD CLASS" records>>> for array classes, called e.g. "Foo[]" and "char[]". That's>>> great (back in the day, no such class objects existed), but>>> the fact of their existance isn't documented. Neither is the>>> naming convention. This might be a good thing to say, just>>> to make sure it doesn't change in the future. If you want,>>> I can come up with some candidate text.>>>>>>>> If you could come up with some words that would be great.>> I'll file the RFE for this.>>>> I assume you are talking about this 1.5 document:>>>> http://javaweb/~ohair/ws/kto_j2se_tiger/src/share/demo/jvmti/hprof/manual.html >>>> Or in the 1.5 install tree at: demo/jvmti/hprof/manual.html?> > > demo/jvmti/hprof/src/manual.html.> > Maybe just after the Basic Type table (which comes out on> page 10 of 12 for me, just before the "Socket connection> and Communication" heading), it could have something like> this:> > There will be a "LOAD CLASS" tag for type type of each array> in the dump. In the LOAD CLASS record, the class name string ID> will refer to a string with a human-readable name of the array> type that is formatted as the type name would be in Java source> code. Thus, the LOAD CLASS record for the type char[] will> be "char[]", for short[][][] will be "short[][][]" and for> MyType[] will be "MyType[]".
>
> The third issue is maybe something that would bear mentioning
> in the docs. I've noticed that there are "LOAD CLASS" records
> for array classes, called e.g. "Foo[]" and "char[]". That's
> great (back in the day, no such class objects existed), but
> the fact of their existance isn't documented. Neither is the
> naming convention. This might be a good thing to say, just
> to make sure it doesn't change in the future.
>>>>>> The third issue is maybe something that would bear mentioning>>> in the docs. I've noticed that there are "LOAD CLASS" records>>> for array classes, called e.g. "Foo[]" and "char[]". That's>>> great (back in the day, no such class objects existed), but>>> the fact of their existance isn't documented. Neither is the>>> naming convention. This might be a good thing to say, just>>> to make sure it doesn't change in the future. If you want,>>> I can come up with some candidate text.>>>>>>>> If you could come up with some words that would be great.>> I'll file the RFE for this.>>>> I assume you are talking about this 1.5 document:>>>> http://javaweb/~ohair/ws/kto_j2se_tiger/src/share/demo/jvmti/hprof/manual.html >>>> Or in the 1.5 install tree at: demo/jvmti/hprof/manual.html?> > > demo/jvmti/hprof/src/manual.html.> > Maybe just after the Basic Type table (which comes out on> page 10 of 12 for me, just before the "Socket connection> and Communication" heading), it could have something like> this:> > There will be a "LOAD CLASS" tag for type type of each array> in the dump. In the LOAD CLASS record, the class name string ID> will refer to a string with a human-readable name of the array> type that is formatted as the type name would be in Java source> code. Thus, the LOAD CLASS record for the type char[] will> be "char[]", for short[][][] will be "short[][][]" and for> MyType[] will be "MyType[]".