This bug is a result of the last change to ops/core.ops (1.368).
Checking out version 1.367 made everything run smoothly. Maybe the
change should be undone? Leo?

The test code I provided still blew up, but that was because of how
I'd return it. I rewrote correctly (and have attached the file), but I
wasn't sure where to place the test.

-- 
matt

Attachment: language.pir
Description: Binary data

Reply via email to