I recall that John fixed a similar issue a while ago.
Yes, this has been fixed.
Usually this kind of "OOPS" has little impact to the final output.
Right-- don't worry about it. We could simply suppress these messages but then we'd never learn about the underlying bugs.
Actually it might be useful for us to teach C-Reduce not to emit these messages if the C-Reduce release is more than 6 months old (and therefore not the latest release). What do you think Yang and Eric?
John