Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8985407
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 15, 20262026-06-15T21:19:24+00:00 2026-06-15T21:19:24+00:00

This ugly piece of code does compile but throws NPE if s == null

  • 0

This ugly piece of code does compile but throws NPE if s == null

public static boolean isNullOrEmpty(String s)
{
    return s != null ? s.isEmpty() : null;
}

while this does not (as expected):

public static boolean isNullOrEmpty(String s)
{
    if(s != null)
        return s.isEmpty();
    else
        return null;
}

I know both of them are plainly wrong, but as I found the first piece of code in our sources, I was quite surprised it did compile.

Edit:
Here’s the relevant part of the JLS from Java 7. I guessed the first statement would apply but the bold one does.

15.25 Conditional Operator ? :

[…]

The type of a conditional expression is determined as follows:

[…]

  • If one of the second and third operands is of primitive type T, and the type of the other is the result of applying boxing conversion (§5.1.7) to T, then the type of the conditional expression is T.

[…]

  • Otherwise, the second and third operands are of types S1 and S2 respectively. Let
    T1 be the type that results from applying boxing conversion to S1, and let T2 be
    the type that results from applying boxing conversion to S2.
    The type of the conditional expression is the result of applying capture
    conversion (§5.1.10) to lub(T1, T2) (§15.12.2.7).
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-15T21:19:25+00:00Added an answer on June 15, 2026 at 9:19 pm

    The first has a ternary operator which has a result type of Boolean. The NPE is converting a null to a boolean.

    It is actually something like:

    Boolean temp = s != null ? s.isEmpty() : null; //no problems here
    return temp; //crash when temp==null
    

    The second is trying to return a wrong type (Object instead of primitive) – and thus does not compile.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I already have this piece of functioning code, but after writing it I did
I have this ugly piece of code.. orders = got_something_from_db() if orders: for order
I have this piece of code : Dictionary<string, object> tempDict = new Dictionary<string, object>();
I have a particularly ugly piece of test code that is calling a number
I got a piece of code like this: foo = None def outer(): global
I have an ugly piece of Serial Port code which is very unstable. void
Let's say I have the following piece of code. To test this, I change
I have a ugly piece of code that adds event handlers. The problem is,
I have this piece of code that searches for a folder given a starting
I don't know how to implement this piece of Python code in Clojure for

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.