Findbugs 给出“System.out 的空指针取消引用”，为什么？

发布于 2024-11-19 00:46:51 字数 339 浏览 3 评论 0 原文

我正在使用 Java 1.7、Eclipse 3.7 以及市场上的 FindBugs 插件。这个例子就像天堂一样好：

class Application
{
  public static void main( String[] args )
  {
    System.out.println( "Bla" );
  }
}

这个消息在过去不存在，内部实现总是在系统中：

public final static PrintStream out = null;

所以Findbugs是正确的，但是现在出现这个消息有什么变化吗？

原文

I am using Java 1.7, Eclipse 3.7 with the FindBugs plugin from the marketplace. The example is as nice as heaven:

class Application
{
  public static void main( String[] args )
  {
    System.out.println( "Bla" );
  }
}

This message was not present in the past and the internal implementation was always in System:

public final static PrintStream out = null;

So Findbugs IS right, but did something change that the message occur now?

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

森林很绿却致人迷途 2024-11-26 00:46:51

因为在java 6中它看起来像这样：

public final static PrintStream out = nullPrintStream();

/**
 * The following two methods exist because in, out, and err must be
 * initialized to null.  The compiler, however, cannot be permitted to
 * inline access to them, since they are later set to more sensible values
 * by initializeSystemClass().
 */
private static PrintStream nullPrintStream() throws NullPointerException {
    if (currentTimeMillis() > 0) {
        return null;
    }
    throw new NullPointerException();
}

所以我猜他们在java 7中简化了它并向编译器添加了一些异常。

JVM 管理本机代码中的 out、in 和 err，因此它给出的错误消息是毫无意义的。

Because in java 6 it looked like this:

public final static PrintStream out = nullPrintStream();

/**
 * The following two methods exist because in, out, and err must be
 * initialized to null.  The compiler, however, cannot be permitted to
 * inline access to them, since they are later set to more sensible values
 * by initializeSystemClass().
 */
private static PrintStream nullPrintStream() throws NullPointerException {
    if (currentTimeMillis() > 0) {
        return null;
    }
    throw new NullPointerException();
}

so I guess they simplified it in java 7 and added some exceptions to the compiler.

JVM manages out, in, and err in native code, so this error message it gives is pointless.

回复收藏 0 原文