|
From: <pcm...@us...> - 2008-06-13 05:31:11
|
Revision: 862
http://javapathfinder.svn.sourceforge.net/javapathfinder/?rev=862&view=rev
Author: pcmehlitz
Date: 2008-06-12 22:31:09 -0700 (Thu, 12 Jun 2008)
Log Message:
-----------
* removed the Dynamic/StaticFields hierarchy, Fields now get directly instantiated. This seemed to be
appropriate to enable data type specific Fields, even though they are probably more suitable for
arrays, and we already have ArrayFields. But having type and role specific Fields hierarchies at the same
time is bad. The only place where the Dynamic/Static roles were required, was the setAttrs() - in
case the fields didn't have attrs yet it could create them on-the-fly. Now the ElementInfo.setXAttrs()
have to do this, which isn't ideal, but therefore we might save a superfluous clone (in case somebody
sets a null attribute value in an object that didn't have attrs yet)
* added Verify.get/setStaticFieldAttr() methods, just for completeness sake
Modified Paths:
--------------
branches/v5/src/gov/nasa/jpf/jvm/DefaultFieldsFactory.java
branches/v5/src/gov/nasa/jpf/jvm/DynamicArea.java
branches/v5/src/gov/nasa/jpf/jvm/ElementInfo.java
branches/v5/src/gov/nasa/jpf/jvm/Fields.java
branches/v5/src/gov/nasa/jpf/jvm/JPF_gov_nasa_jpf_jvm_Verify.java
branches/v5/src/gov/nasa/jpf/jvm/Verify.java
branches/v5/test/gov/nasa/jpf/jvm/TestAttrs.java
Removed Paths:
-------------
branches/v5/src/gov/nasa/jpf/jvm/DynamicFields.java
branches/v5/src/gov/nasa/jpf/jvm/StaticFields.java
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|