[Soot-list] Any language specification for Jimple?

[Eric Bodden]

Hello Sai.

You will find information about Jimple in some early publications here
on this list:
http://www.sable.mcgill.ca/publications/

You also find a Jimple grammar in Soot's source distribution. So that
at least clarifies the syntax. With respect to variable names there
are no restrictions, i.e., the concrete name of a variable should
never matter. It may be the case that certain Java-to-Jimple frontends
use a certain naming scheme like r(i++) but this does not have to be
the case. The only thing one should make sure when generating a new
variable is to take a fresh name that has not yet been assigned. But
then, there's actually a generator that does this for you:
http://www.sable.mcgill.ca/soot/doc/soot/javaToJimple/LocalGenerator.html

Eric

--
Dr. Eric Bodden
Software Technology Group, Technische Universität Darmstadt, Germany
Tel: +49 6151 16-5478    Fax: +49 6151 16-5410
Mailing Address: S2|02 A209, Hochschulstraße 10, 64289 Darmstadt



On 12 April 2010 09:01, Sai Zhang <racezhang at gmail.com> wrote:
> Hi all:
>
> I am wondering is there any language specification for Jimple (as well
> as the translation mechanism from class to jimple)?
>
>  I am interested in knowing how does soot translate class
> to jimple file?  A simplest example is that: at the beginning of each Jimple
> method.
> there are always the assignment of @this and @parameter
>
> r0 := @this: VectorUtils;
> r1 := @parameter0: java.util.Vector;
> r2 := @parameter1: java.util.Vector;
>
> for instance, I want to make sure whether the nams of the JimpleLocals
> are always following the convention of "r0, r1, r2, ..."?
>
> Also, sometimes, I find the naming of JimpleLocals inside the method
> is a bit messy, seems to be no rules. Particularly when involving with
> exception handling..
>
>
> thanks
>
> -Sai
>
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>
>