<assert.h>(P) POSIX Programmer's Manual <assert.h>(P)
NAME
assert.h - verify program assertion
SYNOPSIS
#include <assert.h>
DESCRIPTION
The <assert.h> header shall define the assert() macro. It refers to the macro NDEBUG which is not defined in the header. If NDEBUG is
defined as a macro name before the inclusion of this header, the assert() macro shall be defined simply as:
#define assert(ignore)((void) 0)
Otherwise, the macro behaves as described in assert().
The assert() macro shall be redefined according to the current state of NDEBUG each time <assert.h> is included.
The assert() macro shall be implemented as a macro, not as a function. If the macro definition is suppressed in order to access an actual
function, the behavior is undefined.
The following sections are informative.
APPLICATION USAGE
None.
RATIONALE
None.
FUTURE DIRECTIONS
None.
SEE ALSO
The System Interfaces volume of IEEE Std 1003.1-2001, assert()
COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technol-
ogy -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of
Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE
and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained
online at http://www.opengroup.org/unix/online.html .
IEEE /The Open Group 2003 <assert.h>(P)
Check Out this Related Man Page
assert.h(3HEAD) Headers assert.h(3HEAD)NAME
assert.h, assert - verify program assertion
SYNOPSIS
#include <assert.h>
DESCRIPTION
The <assert.h> header defines the assert() macro. It refers to the macro NDEBUG which is not defined in the header. If NDEBUG is defined as
a macro name before the inclusion of this header, the assert() macro is defined simply as:
#define assert(ignore)((void) 0)
Otherwise, the macro behaves as described in assert(3C).
The assert() macro is redefined according to the current state of NDEBUG each time <assert.h> is included.
The assert() macro is implemented as a macro, not as a function. If the macro definition is suppressed in order to access an actual func-
tion, the behavior is undefined.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Standard |
+-----------------------------+-----------------------------+
SEE ALSO assert(3C), attributes(5), standards(5)SunOS 5.11 10 Sep 2004 assert.h(3HEAD)
Hello,
I have a file like this:
FILE.TXT:
(define argc :: int)
(assert ( > argc 1))
(assert ( = argc 1))
<check>
#
(define c :: float)
(assert ( > c 0))
(assert ( = c 0))
<check>
#
now, i want to separate each block('#' is the delimeter), make them separate files, and then send them as... (5 Replies)
Hi there,
I am a bit puzzled by a weird behavior of Vi. I very simply would like to add increased numbers in some files. Since I have many thousands entries per file and many files, I would like to macro it in vi.
To do this, I enter the first number ("0001") on the first line and then yank... (4 Replies)