• Top
  • Documentation
  • Books
  • Boolean-reasoning
  • Projects
  • Debugging
  • Community
  • Std
  • Proof-automation
  • Macro-libraries
  • ACL2
    • Theories
    • Rule-classes
    • Proof-builder
    • Recursion-and-induction
    • Hons-and-memoization
    • Events
    • Parallelism
    • History
    • Programming
      • Defun
      • Declare
      • System-utilities
      • Stobj
      • State
      • Mutual-recursion
      • Memoize
      • Mbe
      • Io
      • Defpkg
      • Apply$
      • Loop$
      • Programming-with-state
      • Arrays
      • Characters
      • Time$
      • Defconst
      • Fast-alists
      • Defmacro
      • Loop$-primer
      • Evaluation
      • Guard
      • Equality-variants
      • Compilation
      • Hons
      • ACL2-built-ins
      • Developers-guide
      • System-attachments
      • Advanced-features
      • Set-check-invariant-risk
      • Numbers
      • Efficiency
      • Irrelevant-formals
      • Introduction-to-programming-in-ACL2-for-those-who-know-lisp
      • Redefining-programs
      • Lists
      • Invariant-risk
      • Errors
        • Er
        • Value-triple
        • Error-checking
        • Error-triple
        • Assert-event
        • Set-warnings-as-errors
        • Hard-error
        • Set-inhibit-er
        • Must-fail
        • Assert!-stobj
        • Error1
        • Breaks
        • Must-eval-to
        • Ctx
        • Ctxp
        • Assert!
        • Must-succeed
        • Assert$
        • Illegal
        • Er-progn
        • Er-hard
        • Must-succeed*
        • Toggle-inhibit-er
        • Er-soft+
        • Break$
        • Assert*
        • Assert?
        • Er-soft-logic
        • Er-hard?
        • Must-fail-with-soft-error
        • Must-fail-with-hard-error
        • Must-fail-with-error
        • Must-eval-to-t
        • Er-soft
        • Convert-soft-error
        • Toggle-inhibit-er!
        • Set-inhibit-er!
        • Must-prove
        • Must-not-prove
        • Must-fail!
        • Must-be-redundant
        • Must-succeed!
        • Must-fail-local
        • Assert-equal
      • Defabbrev
      • Conses
      • Alists
      • Set-register-invariant-risk
      • Strings
      • Program-wrapper
      • Get-internal-time
      • Basics
      • Packages
      • Oracle-eval
      • Defmacro-untouchable
      • <<
      • Primitive
      • Revert-world
      • Unmemoize
      • Set-duplicate-keys-action
      • Symbols
      • Def-list-constructor
      • Easy-simplify-term
      • Defiteration
      • Fake-oracle-eval
      • Defopen
      • Sleep
    • Operational-semantics
    • Real
    • Start-here
    • Miscellaneous
    • Output-controls
    • Bdd
    • Macros
    • Installation
    • Mailing-lists
  • Interfacing-tools
  • Hardware-verification
  • Software-verification
  • Math
  • Testing-utilities

• Errors

Er-soft+

Print an error message and ``cause an error''

See er for relevant background.

General Form:
(er-soft+ ctx erp val fmt-string arg1 arg2 ... argk)

The form above has essentially the same effect as the following.

(er soft ctx fmt-string arg1 arg2 ... argk)

Both expressions generate logic-mode code, though the latter generates a stronger guard proof obligation. (At one time, the latter generated program-mode code, which likely was why er-soft+ was introduced.) Unlike calls (er soft ...),, the call of er-soft+ returns the error-triple (mv erp val state) instead of always returning (mv t nil state). Note that if erp is nil then this error-triple does not signify an error.

A related utility that always returns (mv t nil state) is er-soft-logic.