[Javapathfinder-svn] SF.net SVN: javapathfinder:[1699] branches/mango/MangoJPF

[<fra...@us...>]

Revision: 1699
          http://javapathfinder.svn.sourceforge.net/javapathfinder/?rev=1699&view=rev
Author:   frankrimlinger
Date:     2009-06-29 05:06:49 +0000 (Mon, 29 Jun 2009)

Log Message:
-----------
Rewiring of MangoJPF to call ClassUtil.getFormalPeer and MethodUtil.getFormalPeer in progress.  As expected, a number of subtle issues are involved.  The ideal of aliasing the class names of System classes is ugly, and will stunt the growth of the formal system code.  A much better solution would be to have a separate class loader for loading the formal system classes, so that the namespace collision problem goes away.  However, jpf would have to be aware of this classloader as a critical requirement is that the formal system classes are also interpreted and processed at the jpf level.  So for now just plow ahead with the stop-gap solution with a view to developing a precise feature request for jpf.  

Modified Paths:
--------------
    branches/mango/MangoJPF/Mango/src/mango/worker/Mango.java
    branches/mango/MangoJPF/javapathfinder-mango-bridge/mango/scanner/ClassUtil.java
    branches/mango/MangoJPF/javapathfinder-mango-bridge/mango/scanner/CodeSurvey.java
    branches/mango/MangoJPF/javapathfinder-mango-bridge/mango/scanner/InvocationUtil.java
    branches/mango/MangoJPF/javapathfinder-mango-bridge/mango/scanner/MethodUtil.java
    branches/mango/MangoJPF/javapathfinder-mango-bridge/mango/scanner/bytecode/ALOAD.java
    branches/mango/MangoJPF/javapathfinder-mango-bridge/mango/scanner/bytecode/INVOKEVIRTUAL.java


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.