view src/testdir/test108.ok @ 10783:04eb70c77cf4 v8.0.0281

patch 8.0.0281: some files are still using ARGSUSED instead of UNUSED commit https://github.com/vim/vim/commit/1266d678bf2ed5072cca9381409536406f8d7b32 Author: Bram Moolenaar <Bram@vim.org> Date: Wed Feb 1 13:43:36 2017 +0100 patch 8.0.0281: some files are still using ARGSUSED instead of UNUSED Problem: MS-Windows files are still using ARGSUSED while most other files have UNUSED. Solution: Change ARGSUSED to UNUSED or delete it.
author Christian Brabandt <cb@256bit.org>
date Wed, 01 Feb 2017 13:45:04 +0100
parents 8fc60af6dbf5
children a527110d5f56
line wrap: on
line source




- show backtrace:

  2 function Foo[2]
  1 Bar[2]
->0 Bazz
line 2: let var3 = "another var"

show variables on different levels:

6
  2 function Foo[2]
->1 Bar[2]
  0 Bazz
line 2: let var3 = "another var"
3
->2 function Foo[2]
  1 Bar[2]
  0 Bazz
line 2: let var3 = "another var"
1

- undefined vars:

undefined var3 on former level:
Error detected while processing function Foo[2]..Bar[2]..Bazz:
line    3:
E121: Undefined variable: var3
E15: Invalid expression: var3
here var3 is defined with "another var":
another var

undefined var2 on former level
Error detected while processing function Foo[2]..Bar:
line    3:
E121: Undefined variable: var2
E15: Invalid expression: var2
here var2 is defined with 10:
10

- backtrace movements:

  1 function Foo[2]
->0 Bar
line 3: End of function

next command cannot go down, we are on bottom

frame is zero

next command cannot go up, we are on top

frame at highest level: 1
->1 function Foo[2]
  0 Bar
line 3: End of function
fil is not frame or finish, it is file
"[No Name]" --No lines in buffer--

- relative backtrace movement

  1 function Foo[2]
->0 Bar
line 3: End of function
->1 function Foo[2]
  0 Bar
line 3: End of function

- go beyond limits does not crash

frame at highest level: 1
->1 function Foo[2]
  0 Bar
line 3: End of function
frame is zero
  1 function Foo[2]
->0 Bar
line 3: End of function

- final result 19:
19