File: ABORT_bang_.html

package info (click to toggle)
acl2 3.1-1
  • links: PTS
  • area: main
  • in suites: etch, etch-m68k
  • size: 36,712 kB
  • ctags: 38,396
  • sloc: lisp: 464,023; makefile: 5,470; sh: 86; csh: 47; cpp: 25; ansic: 22
file content (18 lines) | stat: -rw-r--r-- 802 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
<html>
<head><title>ABORT_bang_.html  --  ACL2 Version 3.1</title></head>
<body text=#000000 bgcolor="#FFFFFF">
<h2>ABORT!</h2>to return to the top-level of ACL2's command loop
<pre>Major Section:  <a href="MISCELLANEOUS.html">MISCELLANEOUS</a>
</pre><p>

When <code>(abort!)</code> is evaluated inside of ACL2's command loop, the
current computation is aborted and control returns to the top of
the command loop, exactly as though the user had interrupted
and aborted the current computation.
<p>
Logically speaking, <code>(abort!) = nil</code>.  But imagine that it is 
defined in such a way that it causes a stack overflow or other
resource exhaustion when called.
<br><br><br><a href="acl2-doc.html"><img src="llogo.gif"></a> <a href="acl2-doc-index.html"><img src="index.gif"></a>
</body>
</html>