Looks like some Neko exception is raised, and when NekoML is trying to match it with "Invalid", it causes an error. I should try to fix this problem in NekoML generator.
This problem is fixed on CVS.Now when NekoML catch a Neko error (mostly strings) it will wrap it using the Neko_error exception constructor so they can be matched normaly.
Nicolas -- Neko : One VM to run them all (http://nekovm.org)
