始终要确保您不是在访问空指针。
显然，SOAP分离并不同于空指针。
确保您不是在访问空指针。
相反，它是用空指针替代。
可能是泄漏、空指针或者错误的内存使用。
There might be leaks, dangling Pointers, or incorrect memory usage.
空指针异常将决不会被完全根除。
Null-pointer exceptions will never be completely eradicated.
这些是空指针，还是指针地址0 ？
空指针到处都有！
两种类型的空指针有时不同。
Null Pointers for two different types are sometimes different.
这些指向入口点的非空指针可实现xa _例程。
These non-null Pointers to entry points implement the xa_ routines.
此外，它并不指出在代码的何处这个空指针被赋值。
Furthermore, it says nothing about where in the code the null pointer was actually assigned.
程序包含一个空指针引用。
访问空指针是非常危险的，因为它可能使您的程序崩溃。
Accessing the null pointer is very dangerous, as it might crash your program.
遗憾的是，许多设计者并没有认识到空指针或空对象带来的危害。
Unfortunately, many designers have still not learnt that the special null pointer or null object is an equally bad idea.
空指针错误通常是一个或多个程序员假设出错的结果。
Null pointer errors are usually the result of one or more programmer assumptions being violated.
它的目的是避免使用空子符串调用Web服务而出现空指针异常。
This code is included in the code which handles the click event for the Invoke Service button and its purpose is to avoid a null pointer exception when the web service is invoked with an empty string.
在许多空指针异常中，真正的错误出现在变量被赋为空值的地方。
In many null-pointer exceptions, the true bug occurs where the variable is actually assigned to null.
因为空指针异常更难诊断，这种“修正”实际上会降低代码的质量。
Because null-pointer exceptions are more difficult to diagnose, this "fix" would actually decrease the quality of the code.
我前面说过，空链表就是两个域都包含一个空指针的LinkedList。
I said earlier that an empty list is a LinkedList containing a null pointer in both fields.
系统级错误包括语法错误、空指针异常、web服务超时、数据库连接超时等。
The system level error includes syntactical error, null pointer exception, web service timeout, database connection timeout, and so on.
此结构包含资源管理器的名称、指向资源管理器入口点的非空指针、标志和版本号。
This structure contains the resource manager's name, non-null pointers to the resource manager's entry points, a flag, and version number.
它在两个域中都放置一个空指针来表示空链表，而不是为空链表定义一个单独的类。
Instead of defining a separate class for empty lists, it represents empty lists by putting a null pointer in both fields.
相反，在运行时发出的错误将会是一个空指针异常而不是类强制转换异常。
Instead, the error signaled at run time would be a null-pointer exception instead of a class-cast exception.
上文有感于与同事关于何时探测空指针和是怎么让程序一下子崩溃了的一次对话。
The text above was inspired by a conversation with some colleagues regarding when to detect a NULL pointer and when simply let the software crash.
我们将探讨的第一个关于空指针异常的错误类型，是一个我称之为悬挂复合类型的错误类型。
The first bug pattern relating to null-pointer exceptions that we'll explore is one that I call the Dangling Composite pattern.
例如，不像一个类转型异常，空指针异常不给出它所需要的内容的任何信息，只有一个空指针。
Unlike, for example, a class-cast exception, a null-pointer exception says nothing about what was expected instead of the null pointer.
Sun的JSFRI期望，在组件没有渲染器的时候，渲染器会发送一个空指针异常。
Sun's JSF RI expects a renderer will send a null pointer exception if your component doesn't have a renderer.
通过指针映射集和故障模型，可以自动检测空指针引用内存故障，提高了测试效率。
Through pointer mapping set and fault model, it can detect null pointer dereference faults automatically and increases the testing efficiency.
不幸的是，自动控制理论告诉我们，没有工具可以静态地决定哪些程序将抛出空指针异常。
Unfortunately, automata theory tells us that no tool could ever statically determine which programs will throw null-pointer exceptions.
不幸的是，自动控制理论告诉我们，没有工具可以静态地决定哪些程序将抛出空指针异常。
Unfortunately, automata theory tells us that no tool could ever statically determine which programs will throw null-pointer exceptions.
应用推荐