3 ms·

Thanks! The one downside is that the local variables that are in scope (and heavily used) in the opcode handlers are all in a different file, which is super wei

by haldean 13y ago

Thanks! The one downside is that the local variables that are in scope (and heavily used) in the opcode handlers are all in a different file, which is super weird, but. On the other hand, I get the performance advantage of the switch statement jump table and, like you said, it's a lot easier to find whatever I'm looking for. I think it turned out a net win.

brianfryer 13y ago
The README is completely broken in movie devices due to everything being inside the `code` block :(
- voltagex_ 13y ago
  I'd say that's a GitHub bug, not a code-specific bug - maybe try contacting support (with app details and a screenshot)
  - haldean 13y ago
    Oh wow, yeah; just checked and it does look pretty crap. I agree that it's a Github bug though; if they allowed zooming on that page it would be fine.
- haldean 13y ago
  What are movie devices? The README is bare text; I like my READMEs to look as good in vim as they do on Github :)
  - userbinator 13y ago
    What autocorrect thinks of "mobile devices", I guess. But people do use them an awful lot for watching movies too...