On Sun, Oct 1, 2023 at 11:24 AM Ernie Rael <err...@raelity.com> wrote:
> On 23/10/01 8:02 AM, shane qian wrote: > > 1. we may ask core members to vote, if class is just a struct then no all > of those arguments. these were all gone. :smile: > > 2. it was just saying **default** was to be `public`, didn't mean no > `private`. > > 3. if `new()` is accessed only by `new C`, empty()/length() perhaps can be > limited to only internal use too. > > I haven't yet looked at the empty()/len() addition; this *was* in the > todo list. I'm guessing this allows the programmer to do > > class C... > len(obj_of_type_C) > > and get a value defined by the class, could be very handy for a class that > is used as a container. Not sure what happens if class didn't define a > __len function; guess I'll find out. > > What I don't understand is why these spec changes are needed at the last > minute. Seems better to add them after 9.1 is released. > If we decide to use "__" for these methods in a future release, then we need to reserve them now. As the changes are small, instead of just reserving the "__" prefix for now, I went ahead with the implementation. - Yegappan > > Unless the idea is to wait several months to shake out these new > additions. Something being in the todo list does not always imply it gets > into a release. Unless it's a simple change, I'd think that stuff would go > in at the beginning of the release cycle and not the end. > > -ernie > > > anyway, let's listen someone else if there were, or I am worried what's > the end this OOP of vim9 how it would be easy to use. > // and sorry I am actually not sure why I was joining to argue this too, > aha... maybe there no job to bother me. :lol: > > -- -- 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 vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAAW7x7n-L22BDyDSZc8ejO1Y6x5k_CsJCO%2B_aaSf%3DSHG_Vtikg%40mail.gmail.com.
