WLPROP introduces dead CONDFUNs

Bugzilla Link	1065
Created on	Apr 19, 2013 21:11
Resolution	FIXED
Resolved on	May 19, 2013 22:06
Version	svn
OS	Linux
Architecture	PC

Extended Description

I am not sure if this is intentional behavior, or if it's entirely
wrong. WLPROP generates new COND_FUNs, leaving the old one in the syntax
tree, bereft of any callers. 
This makes the syntax tree grow. And grow. And grow.
What I see happening is that we have the following calling tree:
 main() -> Loop() -> Cond()
GLF is putting Cond() onto FUNDEF_NEXT( Loop), rather than
on FUNDEF_NEXT( main).
Not what we were hoping for. Likely a day-0 bug in GLF.
A typical failing example is the LACS unit test bugipbb.sac,
but I'll bet they all do this.