| This may or may not be possible, depending on certain factors. First, assume that this would cause a paradox, basically, an exception of type CausalityFailException. If the universe has runtime checking, you go back in time, eliminate Howard, all those people, and then they never existed, your motivation never existed, and you can't have gone back in time. Basically, the stack of history is now in an unknown state and calculating the state of the universe causes the temporal stack to overflow. XX/YY/ZZZZ AA:BB:CC ERROR: Exception thrown: "Unknown Timepoint" CAUSED BY:
XX/YY/ZZZZ AA:BB:CC Nested Exception: "TemporalStackOverflow" CAUSED BY:
XX/YY/ZZZZ AA:BB:CC Nested Exception: "CausalityFailException" CAUSED BY: yummyfajitas:1234224578783 IF, however, the universe had compile-time checking, you'd get a simple, much cleaner
13/12/2010 09:43:23 ERROR: Cannot compile module "yummyfajitas-timetravel" - Method "EliminateTheFuckwits" has uncaught Temporal Side-Effects. This leads us to believe that any language which can do compile-time checking is necessarily better for debugging, quality, and universe stability. (In other words: God used Scala.) |