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

  • SEARCH
  • Home
  • 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 654267
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T22:28:33+00:00 2026-05-13T22:28:33+00:00

what behaviour can I expect when I run this code: do while(testA) { //

  • 0

what behaviour can I expect when I run this code:

do while(testA) {

    // do stuff

} while(testB);

Will it behave like:

do {
    while(testA) {
        // do stuff
    }    
} while(testB);

Or:

if(testA) {
    do {
        // do stuff
    } while(testA && testB);
}

Or something totally unexpected?

I ask this question because I think this is quite ambiguous, and for other people searching on this topic, not because I am lazy to test it out.

  • 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-05-13T22:28:34+00:00Added an answer on May 13, 2026 at 10:28 pm

    It is equivalent to your first block:

    do {
        while(testA) {
            // do stuff
        }    
    } while(testB);
    

    The relevant parts of the Java grammar when parsing this are:

    DoStatement:
        do Statement while ( Expression ) ;
    
    Statement:
        WhileStatement
    
    WhileStatement:
        while ( Expression ) Statement
    
    Statement:
        Block
    
    Block:
        { BlockStatements_opt }
    

    You can see that the Java compiler will parse this as do <WhileStatement> while ( Expression ) ;. That’s the only valid way to parse the code that you wrote.

    Keep in mind that it doesn’t have any special rule to parse this construct. It just ends up being confusing for a human to read due to the unusual way the do-while loop is written. In normal usage do-while is always written as do { ... } while with explicit curly braces.

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

Sidebar

Related Questions

I have run into a very strange behaviour I can’t make sense of. I
I wonder why something like this wouldn't work (actually doesn't work): 4.php : <php
Can the behaviour of pin_ptr be achieved directly in C++/CLI? For example, is it
How can I create a fubumvc behaviour that wraps actions with a particular return
I can't understand the strange behaviour of sessions in CakePHP controller: class UsersController extends
Can some please explain the behaviour below, where, with a from date of 20060301,
Can anyone explain the following behaviour to a relative newbie... const char cInputFilenameAndPath[] =
Possible Duplicate: Behaviour of Sizeof in C Can somebody explain why the following piece
I'm can't figure out some weird behaviour that im getting in the rials console
I came across a strange behaviour with Chrome earlier that I can't seem to

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.