Mercurial > hg > xemacs-beta
comparison src/bytecode.c @ 4978:f48bf636045f
Automatic merge
| author | Ben Wing <ben@xemacs.org> |
|---|---|
| date | Fri, 05 Feb 2010 05:04:43 -0600 |
| parents | fe0d3106cc36 |
| children | 99f8ebc082d9 ed624ab64583 b5df3737028a |
comparison
equal
deleted
inserted
replaced
| 4977:2bf7c51d7101 | 4978:f48bf636045f |
|---|---|
| 119 const Opbyte *program_ptr, | 119 const Opbyte *program_ptr, |
| 120 Opcode opcode); | 120 Opcode opcode); |
| 121 | 121 |
| 122 #ifndef ERROR_CHECK_BYTE_CODE | 122 #ifndef ERROR_CHECK_BYTE_CODE |
| 123 | 123 |
| 124 # define bytecode_assert(x) disabled_assert (x) | 124 /* Normally we would use `x' instead of `0' in the argument list, to avoid |
| 125 # define bytecode_assert_with_message(x, msg) disabled_assert(x) | 125 problems if `x' (an expression) has side effects, and warnings if `x' |
| 126 contains variables or parameters that are otherwise unused. But in | |
| 127 this case `x' contains references to vars and params that exist only | |
| 128 when ERROR_CHECK_BYTE_CODE, and leaving in `x' would result in compile | |
| 129 errors. */ | |
| 130 # define bytecode_assert(x) disabled_assert (0) | |
| 131 # define bytecode_assert_with_message(x, msg) disabled_assert(0) | |
| 126 # define bytecode_abort_with_message(msg) abort_with_message (msg) | 132 # define bytecode_abort_with_message(msg) abort_with_message (msg) |
| 127 | 133 |
| 128 #else /* ERROR_CHECK_BYTE_CODE */ | 134 #else /* ERROR_CHECK_BYTE_CODE */ |
| 129 | 135 |
| 130 # define bytecode_assert(x) \ | 136 # define bytecode_assert(x) \ |
