Re: [Javapathfinder-devel] Problem with peer classes.

[Peter C. M. <Pet...@na...>]

Not sure I understand the problem - vm.peer.packages is an ordered  
list, i.e. you can control which packages are tried first during  
NativePeer lookup

-- Peter



On Nov 11, 2008, at 12:54 PM, Mateusz Ujma wrote:

> Hi,
>
>        In my project (implementing java.util.concurrent) I've
> encountered a problem. We have one example
> that runs ReentrantLock.lock()/unlock() in few concurrent threads, we
> use this to test our performance
> against code from original SDK. When we want to test code from SDK we
> need to change the names
> of our classes, for example  
> JPF_java_util_concurrent_locks_ReentrantLock
> to JPF_java_util_concurrent_locks_ReentrantLock2.
> We could avoid this by setting appropriate vm.peer.packages but the
> problem is that our peer classes
> are in gov.nasa.jpf.jvm package which is always included. One thing  
> that
> we can do is to change the
> package from gov.nasa.jpf.jvm but it seems that my code will not be
> complaint with JPF coding conventions.
> Is there a another solution for that ?
>
> Yours sincerely
>
>    Mateusz Ujma - GSoC student