Mercurial > vim
view runtime/macros/hanoi/poster @ 33532:f99f5a56ff27 v9.0.2015
patch 9.0.2015: Vim9: does not handle islocked() from a method correctly
Commit: https://github.com/vim/vim/commit/4c8da025ef8140168b7a09d9fe922ce4bb40f19d
Author: Ernie Rael <errael@raelity.com>
Date: Wed Oct 11 21:35:11 2023 +0200
patch 9.0.2015: Vim9: does not handle islocked() from a method correctly
Problem: Vim9: does not handle islocked() from a method correctly
Solution: Handle islocked() builtin from a method.
- Setup `lval_root` from `f_islocked()`.
- Add function `fill_exec_lval_root()` to get info about executing method.
- `sync_root` added in get_lval to handle method member access.
- Conservative approach to reference counting.
closes: #13309
Signed-off-by: Christian Brabandt <cb@256bit.org>
Co-authored-by: Ernie Rael <errael@raelity.com>
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Wed, 11 Oct 2023 21:45:04 +0200 |
parents | 3fc0f57ecb91 |
children |
line wrap: on
line source
Article 2913 of alt.sources: Path: oce-rd1!hp4nl!mcsun!uunet!munnari.oz.au!metro!cluster!swift!softway!otc!gregm From: gregm@otc.otca.oz.au (Greg McFarlane) Newsgroups: comp.sources.d,alt.sources,comp.editors Subject: VI SOLVES HANOI Message-ID: <2323@otc.otca.oz> Date: 19 Feb 91 01:32:14 GMT Sender: news@otc.otca.oz Reply-To: gregm@otc.otca.oz.au (Greg McFarlane) Organization: OTC Development Unit, Australia Lines: 80 Xref: oce-rd1 comp.sources.d:5702 alt.sources:2913 comp.editors:2313 Submitted-by: gregm@otc.otca.oz.au Archive-name: hanoi.vi.macros/part01 Everyone seems to be writing stupid Tower of Hanoi programs. Well, here is the stupidest of them all: the hanoi solving vi macros. Save this article, unshar it, and run uudecode on hanoi.vi.macros.uu. This will give you the macro file hanoi.vi.macros. Then run vi (with no file: just type "vi") and type: :so hanoi.vi.macros g and watch it go. The default height of the tower is 7 but can be easily changed by editing the macro file. The disks aren't actually shown in this version, only numbers representing each disk, but I believe it is possible to write some macros to show the disks moving about as well. Any takers? (For maze solving macros, see alt.sources or comp.editors) Greg