Hi all,

Working on a project Feb/Mar using vim9 classes I filed several issues. Each time found a workaround, and went on. Finally ran into

   https://github.com/vim/vim/issues/12089
   vim9class: Calling a base class method through an extending class
   fails #12089

   Also included "Calling a method in an extended class fails" (fixed a
   few days ago)

Put the project back on the shelf, didn't make sense to go on without inheritance. I wonder if it's worth doing 9.1 if classes (inheritance) doesn't work.

Took a quick look at the code in Apr/May, but seemed like too much to take on at the time. Thinking again about moving forward, however slowly, the first thing I thought to do is add some debug commands to vim that would dump class and hierarchy information; adding to the commands as more information was needed. Even the basic structure isn't clear to me and how it evolves to compilation/run-time. The examples in the issue referenced above work at script level, fail in a :def. Does this mean the basic class hierarchy structures are interpreted from script and then combined into some structures that are used by the compiler, are the structures also used during runtime. Anyway, I was encourages to see @yegappan get some things fixed in this area.

I'm not sure how I can best contribute (or, as goes without saying, how much time I'll have). The biggest problem is it looks like a steep learning curve. Looking for any suggestions on getting up to speed enough to contribute.

-ernie

PS I went with here, rather than discussion. Right choice?

--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/51d7532a-be77-2861-1798-f82ef382539a%40raelity.com.

Raspunde prin e-mail lui