These warnings are quite common:

[ strc | info ] Compiling ‘../../../src/str/xrm-front.str’
[ strc | info ] Front-end succeeded : [user/system] = [5.36s/1.62s]
[ strc | info ] Optimization succeeded -O 2 : [user/system] = [0.16s/0.05s]
* warning (MkClosure) expects more than one frame: SDefT(“lifted117”{Offsets(0,0),Closure(“lifted117_cl”),ClosureAlloc},[],[],CallT(SVar(“u_45”{Frames([“lifted117”])}),[],[]))
* warning (MkClosure) expects more than one frame: SDefT(“lifted124”{Offsets(0,0),Closure(“lifted124_cl”),ClosureAlloc},[],[],CallT(SVar(“f_45”{Frames([“lifted124”])}),[],[]))
* warning (MkClosure) expects more than one frame: SDefT(“lifted131”{Offsets(0,0),Closure(“lifted131_cl”),ClosureAlloc},[],[],CallT(SVar(“q_44”{Frames([“lifted131”])}),[],[]))
[ strc | info ] Back-end succeeded : [user/system] = [3.82s/0.57s]
[ strc | info ] Compilation succeeded : [user/system] = [9.35s/2.25s]

Submitted on 3 December 2006 at 14:46

STR-671, martin:
I see this problem popping up frequently. It will probably make users expect that something is really wrong. Therefore it would be good to have this issue fixed before 0.17.

STR-671, visser:
I have changed the debug statements into dbg statemens. So presumably the should now only show up in higher verbosity modes.

Apparently I assumed this situation should not occur when I implemented this, but I wasn’t quite sure when it would occur. Apparently the implementation works fine. It is good to keep the dbg to figure out what is going on exactly. (Too long ago;)

STR-671, visser:
Fixed by making sure the warnings only appear when running compiler in –debug mode. Deferred investigation of the root cause to 0.18 see STR-752