fluffos/docs/lpc/constructs/if.md
Yucong Sun c914f03d66
Add local search and documentation guide for docs site (#1221)
* docs: add local full-text search and a contributor README

Add @easyops-cn/docusaurus-search-local to the Docusaurus site so the
docs get an offline search bar (index built at build time, no external
service). English and zh-CN pages are both indexed, and matched terms
are highlighted on the target page.

Add docs/README.md describing the Docusaurus setup, local dev/build
commands, search behavior, directory layout, and gotchas; exclude it
from the published site alongside CLAUDE.md. Point the root README's
docs/ entry at it.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TSzcESzU9947zkGzQ6SMmE

* docs: remove dead framework leftovers, fix index generation, complete the nav

Delete the VitePress (.vitepress/) and Jekyll (_layouts/, css/) leftovers,
the one-shot migration scripts (fix_md_header.py, fix_seealso.py), and the
stale keywords.json snapshot; prune the matching .gitignore entries and
docusaurus exclude patterns.

Rewrite gen_index.py for Docusaurus: it emitted dead .html links and
legacy 'layout: doc' frontmatter, choked on non-markdown entries, and
dropped nested categories — regenerating an index would have broken it.
It now emits the extension-less links the site actually uses, links
nested category indexes (restoring apply/* on the zh-CN index), and
refuses to run on the docs root. Fix update_index.sh's copy-paste titles
(zh-CN efun/build were titled 'APPLY'), stop it clobbering the
hand-written lpc/index.md, and cover cli/. Regenerated indexes pick up
the missing driver/ffi-plan entry. add_missing_efuns.py now takes the
keywords.json path as an argument instead of requiring a stale copy.

Move CNAME and the Google site-verification file into static/ so they
actually reach the published build output.

Complete the sidebar: link the CLI category to cli/index and add the
missing portbind/symbol/generate_keywords pages, and expose the
previously orphaned stdlib section under Reference.

Promote onBrokenLinks to 'throw' now the build is warning-free, and drop
the empty Demo section from the landing page.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TSzcESzU9947zkGzQ6SMmE

* docs: strip legacy 'layout: doc' frontmatter from all pages

Mechanical sweep removing the Jekyll-era 'layout: doc' line from every
doc page's frontmatter (Docusaurus ignores it), and the matching line
from the templates in docs/CLAUDE.md so new pages don't reintroduce it.
No content changes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TSzcESzU9947zkGzQ6SMmE

---------

Co-authored-by: Claude <noreply@anthropic.com>
2026-07-09 22:09:55 -04:00

2.4 KiB

title
constructs / if

if

The if else statement

LPC's if statement is identical to that provided by C. Syntax is as follows:

if (expression)
    statement;

Alternately:

if (expression) {
    statements;
}

Alternately:

if (expression0) {
    statements;
} else {
    statements1;
}

Alternately:

if (expression0) {
    statements0;
} else if (expression1) {
    statements1;
}

The number of else clauses is not explicitly limited.


Another favorite programming construct is the ? : operator, which also operates identical to C. The syntax is:

expression0 ? expression1_if_true : expression2_if_false

In some cases, ? : is an shorter way of expression constructs such as:

if (expression0)
    var = expression1;
else
    var = expression2;

which can be equivalently translated to:

var = expression0 ? expression1 : expression;

Nullish coalescing operator (??)

LPC also supports expr_left ?? expr_right, which returns expr_left when it is defined and evaluates/returns expr_right only when the left-hand side is undefined (see undefinedp() for what counts as undefined). It short-circuits like ||, but falsy values such as 0, 0.0, "", or ({ }) do not trigger the fallback.

int timeout = cfg["timeout"] ?? 60;          // use default only if key is undefined
string name = player->query_name() ?? "guest";  // RHS runs only when call returns undefined

Operator precedence sits between ?: and ||, mirroring the common pattern lookup ?? fallback without extra parentheses. Use || when you want to treat all falsy values as missing; use ?? when only truly undefined values should fall back.

Logical assignment operators (||=, &&=, ??=)

Short-circuit evaluation is also available in assignment form:

int connected = 0;
object sock = find_connection();

connected ||= open_default();       // assign only if connected is falsy
sock &&= reconnect(sock);           // assign only if sock is truthy
config["timeout"] ??= 60;           // assign only when key is undefined

||= evaluates the right-hand side only when the left-hand side is falsy (0 or 0.0). &&= does the reverse, running the right-hand side only when the left is truthy. ??= mirrors ??: the right-hand side runs only when the left-hand side is truly undefined (useful for lazily populating mappings). The lvalue is evaluated just once in every case.