JVM / Compiler优化对象的未使用属性(optimization of unused properties of object by JVM / Compiler)

 我建议以不同的方式检查文本的值。 将异常抛出的结果根本不是理想的。 
 
 此外，将来包含所有执行该工作的代码会很有帮助。 
 
 
 我建议检查字符串message只包含数字。 我不知道你为什么要将它转换为Long来检查。 假设你在运行consume()时使用了那么长时间，我会将其保存在我的示例中。 
 
 另外，你在isLong中没有使用TextField对象，你应该删除它。 
 
 最后，你通过返回一个你不使用的布尔值而只是在方法中设置一个布尔值而冗余。 让我们清理一下。 
 
 替换isLong(TextField tf, String m)代码isLong(TextField tf, String m)如下 
 
private boolean isLong(String message){
    if (message.matches("[0-9]+")) {
        try {
            long callbackNumberLong = Long.parseLong(message);
            System.out.println("That was a number!");
            return true;
        } catch (NumberFormatException e) {
            System.out.println("That was NOT a number!");
            return false;
        } 
    } else {
        return false;
    }
}
 
 如果你不需要callBackNumberLong作为Long，我建议不要解析它并将它保存为一个字符串。 我有一种感觉，你不会用电话号码做数学。 
 
 所有剩下要做的就是调用isLong(message)来检查isNumber为true，而不是调用isLong(tf, m)然后检查布尔值。 

I suggest checking the value of the text differently. It is not really ideal to base your outcome on exceptions being thrown.
 
Also, in the future it is helpful to include all the code doing the work.
 
 
I suggest checking if the String message only contains numbers. I am not sure why you are converting it to a Long to check that. Assuming you are using that long when you run consume() I will keep it in my example. 
 
Additionally, you are not using a TextField object in isLong, you should remove that.
 
Finally, you are being redundant by returning a boolean that you are not using and just set a boolean within the method. Lets clean that up.
 
Code to replace isLong(TextField tf, String m) is below
 
private boolean isLong(String message){
    if (message.matches("[0-9]+")) {
        try {
            long callbackNumberLong = Long.parseLong(message);
            System.out.println("That was a number!");
            return true;
        } catch (NumberFormatException e) {
            System.out.println("That was NOT a number!");
            return false;
        } 
    } else {
        return false;
    }
}
 
If you do not need callBackNumberLong as a Long, I suggest not parsing it and keeping it as a string. I have a feeling you wont be doing math with a phone number.
 
All that is left to do is call isLong(message) where you were checking if isNumber was true instead of calling isLong(tf, m) then checking the boolean value after.