|
From: <fra...@us...> - 2009-06-11 20:50:49
|
Revision: 1613
http://javapathfinder.svn.sourceforge.net/javapathfinder/?rev=1613&view=rev
Author: frankrimlinger
Date: 2009-06-11 20:50:47 +0000 (Thu, 11 Jun 2009)
Log Message:
-----------
Still working on wonderfully subtle rewriting bug in MangoJPF. Fortunately, a comparison with Mango yields a unification failure very early on. Detailed analysis of exactly what the unifier does in the two different programs is in progress. To reproduce, open the itsAWrap.main predicate transformer in a separate window, then
1. opening up to the first codeSym
2. unconditionally rewrite codeSym
3. turn on hits
4. unconditionally rewrite (o codeSym pathSym)
The trouble is that when pathSym is interpreted, it is supposed to be typed as state. This typing never kicks in MangoJPF, so composition doesn't fire, and the day is lost.
Why?
Modified Paths:
--------------
branches/mango/Mango/Mango/src/mango/worker/engine/events/RewriteEvent.java
branches/mango/Mango/Mango/src/mango/worker/engine/unifier/ActionCallBack.java
branches/mango/Mango/Mango/src/mango/worker/engine/unifier/UnifyEvent.java
branches/mango/Mango/mangoUserHome/frank/rules/rulebase.zip
branches/mango/Mango/mangoUserHome/frank/sessions/a.zip
branches/mango/MangoJPF/Mango/src/mango/worker/engine/events/RewriteEvent.java
branches/mango/MangoJPF/Mango/src/mango/worker/engine/unifier/ActionCallBack.java
branches/mango/MangoJPF/Mango/src/mango/worker/engine/unifier/UnifyEvent.java
Added Paths:
-----------
branches/mango/MangoJPF/mangoUserHome/frank/sessions/baseline/a.zip
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|