这里有一个非常简单的答案:

Runtime and compile time are programming terms that refer to different stages of software program development. In order to create a program, a developer first writes source code, which defines how the program will function. Small programs may only contain a few hundred lines of source code, while large programs may contain hundreds of thousands of lines of source code. The source code must be compiled into machine code in order to become and executable program. This compilation process is referred to as compile time.(think of a compiler as a translator)

用户可以打开并运行编译后的程序。当应用程序正在运行时，它被称为运行时。

术语“运行时”和“编译时”经常被程序员用来指代不同类型的错误。编译时错误是一种问题，例如语法错误或缺少文件引用，从而阻止程序成功编译。编译器产生编译时错误，并通常指出源代码的哪一行导致了问题。

如果一个程序的源代码已经被编译成一个可执行程序，那么它在程序运行时可能仍然有错误。例子包括不能工作的特性、意外的程序行为或程序崩溃。这些类型的问题被称为运行时错误，因为它们发生在运行时。

参考

将源代码转换为“屏幕|磁盘|网络”可以(大致)以两种方式发生;称之为编译和解释。

在编译程序中(例如c和fortran):

源代码被输入到另一个程序(通常称为编译器)，该程序生成一个可执行程序(或一个错误)。 运行可执行文件(通过双击它，或在命令行上键入它的名称)

在第一步发生的事情被称为在“编译时”发生，在第二步发生的事情被称为在“运行时”发生。

在解释程序中(例如MicroSoft basic(在dos上)和python(我想)):

源代码被输入到另一个程序(通常称为解释器)，该程序直接“运行”它。在这里，解释器充当程序和操作系统(或非常简单的计算机中的硬件)之间的中间层。

在这种情况下，编译时和运行时之间的差异很难确定，而且与程序员或用户的关系也小得多。

Java是一种混合，代码被编译成字节码，然后在虚拟机上运行，虚拟机通常是字节码的解释器。

还有一种中间情况，即程序被编译为字节码并立即运行(如在awk或perl中)。

(编辑:以下内容适用于c#和类似的强类型编程语言。我不确定这是否对你有帮助)。

例如，在运行程序之前，编译器(在编译时)将检测到以下错误，并将导致编译错误:

int i = "string"; --> error at compile-time

另一方面，像下面这样的错误不能被编译器检测到。您将在运行时(当程序运行时)收到一个错误/异常。

Hashtable ht = new Hashtable();
ht.Add("key", "string");
// the compiler does not know what is stored in the hashtable
// under the key "key"
int i = (int)ht["key"];  // --> exception at run-time

编译时和运行时之间的差异就是精明的理论家所说的阶段差异的一个例子。它是最难学习的概念之一，特别是对于没有太多编程语言背景的人来说。要解决这个问题，我发现问一下很有帮助

程序满足哪些不变量? 在这个阶段会出现什么问题? 如果阶段成功，后置条件是什么(我们知道什么)? 输入和输出是什么(如果有的话)?

编译时

The program need not satisfy any invariants. In fact, it needn't be a well-formed program at all. You could feed this HTML to the compiler and watch it barf... What can go wrong at compile time: Syntax errors Typechecking errors (Rarely) compiler crashes If the compiler succeeds, what do we know? The program was well formed---a meaningful program in whatever language. It's possible to start running the program. (The program might fail immediately, but at least we can try.) What are the inputs and outputs? Input was the program being compiled, plus any header files, interfaces, libraries, or other voodoo that it needed to import in order to get compiled. Output is hopefully assembly code or relocatable object code or even an executable program. Or if something goes wrong, output is a bunch of error messages.

运行时

We know nothing about the program's invariants---they are whatever the programmer put in. Run-time invariants are rarely enforced by the compiler alone; it needs help from the programmer. What can go wrong are run-time errors: Division by zero Dereferencing a null pointer Running out of memory Also there can be errors that are detected by the program itself: Trying to open a file that isn't there Trying find a web page and discovering that an alleged URL is not well formed If run-time succeeds, the program finishes (or keeps going) without crashing. Inputs and outputs are entirely up to the programmer. Files, windows on the screen, network packets, jobs sent to the printer, you name it. If the program launches missiles, that's an output, and it happens only at run time :-)

对于S.O.来说，这不是一个好问题(这不是一个特定的编程问题)，但总的来说，这不是一个坏问题。

如果您认为这是微不足道的:那么读时与编译时的区别是什么呢?什么时候这是一个有用的区别?编译器在运行时可用的语言呢?Guy Steele(不是笨蛋，他)在CLTL2中写了7页关于EVAL-WHEN的内容，CL程序员可以使用它来控制这一点。两句话只能勉强给出一个定义，而定义本身还远远不够解释。

In general, it's a tough problem that language designers have seemed to try to avoid. They often just say "here's a compiler, it does compile-time things; everything after that is run-time, have fun". C is designed to be simple to implement, not the most flexible environment for computation. When you don't have the compiler available at runtime, or the ability to easily control when an expression is evaluated, you tend to end up with hacks in the language to fake common uses of macros, or users come up with Design Patterns to simulate having more powerful constructs. A simple-to-implement language can definitely be a worthwhile goal, but that doesn't mean it's the end-all-be-all of programming language design. (I don't use EVAL-WHEN much, but I can't imagine life without it.)

关于编译时和运行时的问题空间是巨大的，而且在很大程度上仍未被探索。这并不是说S.O.是进行讨论的正确场所，但我鼓励人们进一步探索这一领域，特别是那些对它应该是什么没有先入为主概念的人。这个问题既不简单也不愚蠢，我们至少可以给检察官指出正确的方向。

不幸的是，我不知道任何好的参考资料。CLTL2稍微讲了一下，但对于学习它并不是很好。

以下是前面类似的问题的答案，运行时错误和编译器错误的区别是什么?

编译/编译时/语法/语义错误:编译或编译时错误是由于键入错误而发生的错误，如果我们没有遵循任何编程语言的正确语法和语义，那么编译器就会抛出编译时错误。除非您删除所有语法错误或调试编译时错误，否则它们不会让您的程序执行一行。 例如:在C语言中缺少分号或将int错误地输入为int。

运行时错误:运行时错误是指程序处于运行状态时产生的错误。这些类型的错误将导致您的程序出乎意料地运行，甚至可能杀死您的程序。它们通常被称为例外。 示例:假设您正在读取一个不存在的文件，将导致运行时错误。

阅读更多关于所有编程错误