4 ms·

Well in the number-script compiler, it verifies code by running it (I'm not sure if that qualifies). Also, you would get stuck on code with infinite loops.

• substack 14y ago
  The verify phase was just defining an inline function but not running it. However, I just noticed that a program with carefully placed braces could jump out of the function box and actually run. I replaced the checker with just Function(src) which shouldn't have that problem and is much faster.
  • mappum 14y ago
    Oh, right, it didn't execute it. I need more caffeine (except not really, it's 2:30).
• icebraining 14y ago
  Also, you would get stuck on code with infinite loops. Or you could just set a timeout.
  • taybin 14y ago
    Then how would you know the loop wouldn't eventually halt? ;)
    • ErikD 14y ago
      You don't: http://en.wikipedia.org/wiki/Halting_problem http://en.wikipedia.org/wiki/Halting_problem
      • taybin 14y ago
        Indeed.
• ajuc 14y ago
  If we only checked that produced program has valid syntax, instead of running it, we won't have problems with loops. Many gibberish programs would be produced, but some usefull also, eventually. We just wouldn't know which ones are the useful ones, but it shouldn't matter for copyright? So it seems documenting is the real work, and programming is something that can be automated :)