view test/compile/shutup-operator-test/bytecode-disp.tst @ 33418:ea29311fbd44 bytecode-interpreter

rename some files for consistency Prefer hyphens over underscores in filenames. * test/compile/shutup-operator-test/@double/display.m: Rename from test/compile/shutup_operator_test/@double/display.m. * test/compile/shutup-operator-test/@logical/display.m: Rename from test/compile/shutup_operator_test/@logical/display.m. * test/compile/shutup-operator-test/bytecode-disp.tst: Rename from test/compile/shutup_operator_test/bytecode_disp.m. * test/compile/shutup-operator-test/bytecode_disp.m: Rename from test/compile/shutup_operator_test/bytecode_disp.tst. * test/compile/module.mk: Update.
author John W. Eaton <jwe@octave.org>
date Tue, 16 Apr 2024 14:33:05 -0400
parents test/compile/shutup_operator_test/bytecode_disp.tst@435cfe35e3c6
children
line wrap: on
line source

## Test display due to no ";" at eol
##
## We are overloading display for double so we place this test
## in its own folder to not mess double up for the other
## tests.

%!testif ENABLE_BYTECODE_EVALUATOR
%! % Overloading of class-methods seems to stick so we need to clear them since we overload
%! % double's display. Is this a bug ???
%! clear classes
%! key = "ans = 1 . ans = 5 . . ans = 0 . ans = 8 . ans = 3 . x = 3 . x = 1 y = 2 . x = 1 . . x = 1 . y = 2 . x = 1 ";
%! __vm_compile__ bytecode_disp clear;
%! bytecode_disp;
%! assert (__prog_output_assert__ (key));
%!
%! assert (__vm_compile__ ("bytecode_disp"));
%! bytecode_disp;
%! assert (__prog_output_assert__ (key));