blobbyblob

Print stack trace when callback fails

1

Switched `lua_call` in `call_lua_direct` to `lua_pcall`. The error handler which is passed in will print the error and traceback, then tear down. This is in preference to crashing.

When an error is encountered in the callback for `watch_for_file_changes`, the program will crash saying `lua5.1.exe has stopped working` rather than providing a useful error message. Repro: ```lua require("winapi") watcher,...