[Soot-list] instrumenting with soot class by class

[Richard L. Halpert]

I recall someone asking about this type of use on the Soot list in the
past.  It might be useful to have a mechanism inside Soot to decide if a
class should be written to file or not... for example if the decision on
whether or not to transform a class needs to be determined by analyzing the
class.  Perhaps...

-Rich

On Fri, Apr 18, 2008 at 12:30 PM, Eric Bodden <eric.bodden at mail.mcgill.ca>
wrote:

> >  I have contemplated that approach, yet I would find it much more
> elegant if
> > Soot would offer a feature that would take care of this particular
> issue.
> >  I am guessing that more people would be interested in this particular
> > performance improvement.
>
> I am not sure. My guess is that most people use Soot for whole program
> analysis and not on a file-by-file basis. But nevertheless there may
> be some people who have use cases similar to yours.
>
> >  So I am contemplating digging into the internals of Soot in order to
> see
> > whether I can implement this feature.
> >  What do you think?
>
> Sure, give it a try and let us know how it works. Depending on
> somebody's Ant skills it's probably not harder than writing an Ant
> script ;-)
>
> Eric
>
> --
> Eric Bodden
> Sable Research Group
> McGill University, Montréal, Canada
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.CS.McGill.CA/pipermail/soot-list/attachments/20080418/6a090c02/attachment.htm