Shared Memory and User Input

Shared Memory objects have been added, as well as preliminary HID input(buttons only)

Is there a reason to catch this exception and then do nothing? At the very least, report an error. Furthermore, you should be doing the “bare-minimum” in a try block, as anything theoretically could raise that exception and you won’t know why.

Which brings me to my stance on exceptions in general: If a library that we use uses exceptions for failures, it obviously makes sense to catch them and handle them. I just don't necessarily think that we should be introducing exceptions for error handling in our own code, and in general I don’t think it makes sense to use them in an emulator just because they make error handling “pretty”. They are very easy to abuse, which could easily lead to performance factors if we start going crazy with them. Furthermore, for reasons like the above code, it’s also very easy to incorrectly use/handle them. And then it’s also very easy to end up with memory/resource leaks via not-so-obvious code paths.