Perfect, thank you very much. It looks pretty good... you obviously have done a lot of work on it. | @DualBrain
@InteXX If you find anything that doesn't work (or is lacking), please let me know.
@pjbdigitalservices Thanks! As for any worries about the future of VB... I have great confidence that Microsoft isn't going to outright abandon VB; I also expect that improvements will still take place. On the other hand, even if such a thing were to occur... it being open-source using the MIT license, I'm not too worried. 😉With that out of the way, the evidence is strong that Microsoft is truly continuing to support (and invest heavily) in VB; the reality is that they aren't going to do "everything" "everyone" wants, so many people are upset that what they want Microsoft to focus on (re: VB and other technologies) isn't what Microsoft feels they should focus on. For example, right now that major focus re: VB is on Windows Forms. A ton of work is taking place there and I can't stress enough how much effort it is actually taking to bring VB over to .NET 5+ related to WinForms given that VB has many "enhancements" that other languages simply do not have. What will take place next? Who knows. On another hand, several things have taken place over the past 12 months as they relate to .NET (core) and/or Roslyn to fix issues related to "just VB" and interop with other languages. The evidence is clear that the support and desire to further VB is there from those on the Microsoft side. Now that that has been said, it is also important to remember that there is a general shift in the developer world that requires that we all transition "or die". What I mean by this is that we have to take ownership of some of what it is we want... thus some of the work I've (and several others have) been doing. 😊
@DualBrain your words about the future of VB are like music to me! You are my hero
Hello guys! Tomorrow is the last Sunday of the month, and guess what happens on that day? DISCLOSURE hahahaha Anyone would like to suggest something?
Not how long I've programmed with BASIC, how have I only just learnt about Shadow being an valid modifier for Class ?
@AdamSpeight2008 It constantly amazes me how I continue to discover things I never knew within the language. 😎To me it's kind of refreshing in some ways; in other ways, it makes you wonder "what else don't I know". 🤔 On a semi-related note: This is one of the main reasons why, at this point, I tend to take a very cautious point of view on anything new/change as it seems like it is almost impossible to know the entire surface areas at this point. 😉
Mohammad Hamdy Ghanem
I never heard of it, nor need it. It is unlikely that I will need a base class A with an internal class Test and a child class B that inherits A, and has an internal class Test that shadows A.Test! This doesn't seem a practical design.
@VBAndCs Me neither but the surprise the language allowed it. The modified Shadowson inherited members I can understand but the inner class that threw me. I don't think I've seen a example of the warning documented any where. Maybe i missed in the vb.net language reference?