daniel

True. I've been working on some use cases _([FSM](https://github.com/d5/go-fsm) and couple other undisclosed projects)_, and, that way I'm learning a lot about the language/script needs, including this exception handling. Tengo...

@earncef: [some initial thoughts](https://github.com/d5/tengo/wiki/Error-Handling-V2) if you're interested. It's not finalized and there are lots of things missing there.

Not directly related to this issue, but, this PR #103 adds more info (filename, line, column) to the runtime errors with little performance overhead. /cc @earncef

Thanks for the PR. I really like the documentation on this change. I thought a lot about adding "methods" in the past, and, I've explored Python-like syntax as well. I...

I've spent some time to try this, but, I'm still not quite convinced if we should make this change. This is a significant change and naturally increases the maintenance costs...

I'm sure there will be more details we will have to figure out, but, I think Go-like "context" construct is better because it's more easily understood and very commonly used...

We should also add `stdout()` if we do this. One thing to note is that sandboxing is important in Tengo. In many cases, direct access to stdin/out/err will be less...

Yeah. `os` package will not be included for most sandboxed environments anyway.

Yes. Please create a new module. It's better for backward compatibility, and it gives more options to people with different requirements.

This project is not in active development to be honest. There are several technical challenges that need to addressed or clarified. See https://github.com/d5/node.native/issues/26 for prior discussion. Just to name a...