Neko exception? Why not get rid of them? Exceptions are a
very bad idea: they're WAY too powerful.
We desire to escape from a context, but in a controlled
way.
Call/cc actually seems better to me.
There is not yet call/cc in Neko.
I don't have big knowledge of it (just through the iterator/yield python
statement) so I'm still thinking about how it should work in Neko, in
terms of both API/Language constructs and implementation. If you have
suggestions I'm open.
After this is done I'll see if it makes sense or not to encode
exceptions in terms of call/cc, but right now I'm really satisfied with
Neko exceptions. They are fast and still provide full backtrace which is
really helpful when debugging. With this and some other features, I'm
fealing now more at ease when programming in NekoML than when
programming in OCaml.
Nicolas
---
Neko : One VM to run them all
