Primitive-type arrays

5 views
Skip to first unread message

Saswat Anand

unread,
Mar 13, 2011, 2:31:50 PM3/13/11
to tamiflex...@googlegroups.com
Hello,

It seems that Tamiflex does not correctly log names of the classes corresponding to primitive-type arrays. For example,  for an invocation, forName("[Z"), it (probably) logs java.lang.Boolean[], which is not correct because the two classes are different. Or am I missing something?

Thanks,
Saswat

Eric Bodden

unread,
Mar 14, 2011, 4:08:08 AM3/14/11
to tamiflex...@googlegroups.com, Saswat Anand
Hi Saswat.

Thanks a lot for your mail, this was indeed a bug. I just committed a
patch. Would you mind checking out the current head and giving it a
try?

Cheers,
Eric

--
Dr. Eric Bodden, http://bodden.de/
Principal Investigator in Secure Services at CASED
Coordinator of the CASED Advisory Board of Study Affairs
PostDoc at Software Technology Group, Technische Universität Darmstadt
Tel: +49 6151 16-5478    Fax: +49 6151 16-5410
Mailing Address: S2|02 A209, Hochschulstraße 10, 64289 Darmstadt

Saswat Anand

unread,
Mar 18, 2011, 3:59:03 PM3/18/11
to Eric Bodden, tamiflex...@googlegroups.com
Hi Eric,

The bug appears to have been fixed.

It is good to see the new java.lang.reflect.Field stuff. Any plans to
handle the two "newInstance" methods of java.lang.reflect.Array?

Saswat

Eric Bodden

unread,
Mar 19, 2011, 3:34:30 AM3/19/11
to tamiflex...@googlegroups.com, Saswat Anand
> It is good to see the new java.lang.reflect.Field stuff. Any plans to
> handle the two "newInstance" methods of java.lang.reflect.Array?

Oh, I did not know those exist. Good point. Yes, we should definitely
include those. I won't have much time to do so within the next few
weeks, though.

Thanks for pointing that out!

Eric

Reply all
Reply to author
Forward
0 new messages