comparison src/ChangeLog @ 4974:fe0d3106cc36

fix compile problems in bytecode.c when no error-check-byte-code (issue 666) -------------------- ChangeLog entries follow: -------------------- src/ChangeLog addition: 2010-02-05 Ben Wing <ben@xemacs.org> * bytecode.c (bytecode_assert): Use 0 instead of x in disabled_assert calls to avoid errors due to using undefined vars/params (they are defined only when ERROR_CHECK_BYTE_CODE, which also turns on/off the asserts).
author Ben Wing <ben@xemacs.org>
date Fri, 05 Feb 2010 04:07:47 -0600
parents 5c89ceb69819
children c5cb3cb79110
comparison
equal deleted inserted replaced
4970:5c89ceb69819 4974:fe0d3106cc36
1 2010-02-05 Ben Wing <ben@xemacs.org>
2
3 * bytecode.c (bytecode_assert):
4 Use 0 instead of x in disabled_assert calls to avoid errors due
5 to using undefined vars/params (they are defined only when
6 ERROR_CHECK_BYTE_CODE, which also turns on/off the asserts).
7
1 2010-02-04 Ben Wing <ben@xemacs.org> 8 2010-02-04 Ben Wing <ben@xemacs.org>
2 9
3 * bytecode.c (assert_failed_with_remembered_ops): 10 * bytecode.c (assert_failed_with_remembered_ops):
4 * bytecode.c (init_opcode_table_multi_op): 11 * bytecode.c (init_opcode_table_multi_op):
5 Declare some things const to shut up G++ v4 warnings. 12 Declare some things const to shut up G++ v4 warnings.