Function Entry: QUIT

← Prev | ↑ Chapter | Next → | Index | Symbols

Function Entry: QUIT

Name

quit

Class

Function

Syntax

(quit)
(quit status)        ; clautolisp extension

Arguments and Values

  • None on AutoCAD / BricsCAD.
  • status (clautolisp extension) — an optional integer process exit status. When omitted, clautolisp uses the pending status recorded by autolisp-set-status (0 when never set); see autolisp-status.

Description

Unconditionally cancels the running LISP code and terminates LISP processing for the current invocation. Bricsys's per-symbol pages distinguish the verb in prose only — exit "exits" the LISP run, quit "cancels" it — but the signature, abort message, and effect on the host are identical. Treat as an alias of exit in implementation.

clautolisp accepts an OPTIONAL integer status argument (the exit-status channel; see autolisp-set-status). (quit N) terminates with exit code N; bare (quit) terminates with the pending status. Supplying the argument is a clautolisp extension: under --strict / --autocad / --bricscad it emits a non-fatal out-of-dialect WARNING (the zero-arg form stays standard and silent).

Return Values

Does not return normally. Channel-level behaviour: prints ; error : quit / exit abort to the prompt.

Side Effects

Aborts the running LISP evaluation; *error* handlers may run as the abort propagates.

Availability

  • AutoCAD 2026: documented (Autodesk Error-Handling Functions Reference).
  • BricsCAD V26: documented (BricsCAD V26 dedicated per-symbol page).
  • Status: documented in both vendors. Phase-5 closure: the BricsCAD per-symbol page nails the previously open question down to "no semantic distinction beyond the verb" — both forms are documented identically and produce the same abort-channel message. The historical hypothesis that some vendor or release distinguished exit and quit is not supported by current vendor evidence.

See Also

  • exit — companion form; identical signature and effect.