[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
note: JasminClass change
Hi all,
I thought I'd get this archived:
Chris Pickett asked soot-list a question a long time ago about Soot's
generation of java.lang.Object classes (e.g. when transforming CLASSPATH).
I looked into it today and noticed that JasminClass always generates a
.super java/lang/Object declaration even if the superclass field is not
set. I changed this so that it wouldn't generate a .super declaration
anymore. I have a vague fear that there was a reason the .super
declaration was there, but not enough to avoid making this change. But
in case it breaks anything, you can talk to me about it.
pat
---------- Forwarded message ----------
Date: Wed, 21 Apr 2004 17:44:42 -0400 (EDT)
From: plam-sable.svn <owner-soot-repos-commits@sable.mcgill.ca>
To: soot-repos-commits@sable.mcgill.ca
Subject: r1430: in soot/trunk/src/soot: baf jimple
Author: plam
Date: 2004-04-21 17:44:38 -0400 (Wed, 21 Apr 2004)
New Revision: 1430
Log:
1. replace SootClass parameter with sootClass parameter (bad naming!)
2. do not emit .super java/lang/Object for java.lang.Object class
in jasmin output
Modified:
soot/trunk/src/soot/baf/JasminClass.java
soot/trunk/src/soot/jimple/JasminClass.java