xref: /src/tests/usr.bin/indent/psym_if_expr_stmt_else.c

/* $NetBSD: psym_if_expr_stmt_else.c,v 1.5.2.1 2025/08/02 05:58:13 perseant Exp $ */

/*
 * Tests for the parser symbol psym_if_expr_stmt_else, which represents the
 * parser state after reading the keyword 'if', the controlling expression,
 * the statement of the 'then' branch and the keyword 'else'.
 *
 * If the next token is an 'if', the formatting depends on the option '-ei' or
 * '-nei'.  Any other lookahead token completes the 'if' statement.
 */

//indent input
void
example(_Bool cond)
{
	if (cond) {}
	else if (cond) {}
	else if (cond) i++;
	else {}
}
//indent end

//indent run
void
example(_Bool cond)
{
	if (cond) {
	}
	else if (cond) {
	}
	else if (cond)
		i++;
	else {
	}
}
//indent end

/*
 * Combining the options '-bl' (place brace on the left margin) and '-ce'
 * (cuddle else) looks strange, but is technically correct.
 */
//indent run -bl
void
example(_Bool cond)
{
	if (cond)
	{
	}
	else if (cond)
	{
	}
	else if (cond)
		i++;
	else
	{
	}
}
//indent end

//indent run-equals-prev-output -bl -nce

/*
 * Adding the option '-nei' (do not join 'else if') expands the code even
 * more.
 */
//indent run -bl -nce -nei
void
example(_Bool cond)
{
	if (cond)
	{
	}
	else
		if (cond)
		{
		}
		else
			if (cond)
				i++;
			else
			{
			}
}
//indent end


/*
 * In many cases, an else-if sequence is written in a single line.
 * Occasionally, there are cases in which the code is clearer when the
 * 'else' and 'if' are in separate lines.  In such a case, the inner 'if'
 * statement should be indented like any other statement.
 */
//indent input
void
example(void)
{
	if (cond)
		stmt();
	else
		if (cond)
			stmt();
}
//indent end

//indent run
void
example(void)
{
	if (cond)
		stmt();
	else if (cond)
		stmt();
}
//indent end